Add ruleset configuration #408
Open
Conversation
This file contains hidden or 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
coorasse
reviewed
May 13, 2025
There was a problem hiding this comment.
Two questions:
- is this an improvement in any direction? the new rulesets offer more flexibility, but if we don't use it, does it mean more complexity for us and we would be perfectly fine with the existing branch protection?
- we were trying to fix the problem that we can push to develop and we don't want that, while allowing everyone to still bypass checks and merge if they want. Is this now tackled?
it's very similar to the classic branch protection. it's not more complex.
yes, you can uncheck |
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.
TICKET-23953
Rulesets are a new feature of GitHub. They are the preffered way of defining protection rules compared to the classic options.
The new Rulesets offer more flexibility and control compared to the "Classic branch protection rules".
We propose that we should embrace the new standard for upcoming repositories.