Tmi2 26/create main branch protection workflow #43
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
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.
Adds workflow, to force merges in main branch only from release branches.
adds "TMI2"(Team mercury tickets) in the feature.yml workflow's branch triggers
Next step:
to enforce it, we would need to go modify the main branch protection:
in GitHub settings-> Branches-> edit the main-> tick Require status checks to pass before merging -> tick Require branches to be up to date before merging -> search for protectMainBranch-> save
This would mean that whenever a pr is raised to merge into main, if it's not from release it will fail the workflow, and we won't be able to merge(the button will be disabled)