Merging feat/1_auth
#126
Closed
seporterfield
started this conversation in
General
Replies: 2 comments
-
Note: If you want to review the current feat/1_auth and look for TODOs, please make issues out of them instead of requesting changes. Now that we have, we can work on those TODOs on |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The start of a new era... Trunk based development!
feat/1_auth
is no longer behindmain
, it is in a mergeable state.We can run
git reset --hard c950471
and push to go back.Let this thread serve as a place for any objections to merging and continuing our trunk-based journey on
main
.We've been treating
feat/1_auth
like our trunk, and we've learned how to use a trunk-based workflow.Let this post serve as a place for any open discussion points before merging. To avoid infinite discussion and more merges into
feat/1_auth
, any objections should be brought up before 2024/06/04 GMT 0000.As of this post
Beta Was this translation helpful? Give feedback.
All reactions