fix: branch name compliance [DEVOP-147] #92
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
callms
changed the title
callms
force-pushed
the
fix/branch-name-compliance
branch
from
34d2f14 to
7db67b0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do? Why?
There is a (probably too) long discussion on
#mobsuccess-architectureregarding branch names.Facts:
This ADR is non-opiniated and has the only purpose of reflecting the current state of decisions that were already made.
Along with changes in this repository, I have also updated the Notion page to emphasize that ADR #9 is the main source of truth, and removed text that no longer reflected our Git usage (like, how we merged before merge queue).