- 
                Notifications
    You must be signed in to change notification settings 
- Fork 4.3k
chore(ci): disable branch protection rules in mergify #35189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Alisen Berat Ozel <null>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(This review is outdated)
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
| - -closed | ||
| - "#approved-reviews-by>=1" | ||
| - -approved-reviews-by~=author | ||
| # This is important! It makes the PR Linter work. | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Arguably these comments are very useful. Can we keep them pls?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is why I kept it do-not-merge, will keep them
| Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). | 
| Comments on closed issues and PRs are hard for our team to see. | 
This change has been made by @ozelalisen from the Mergify Queue Rule Configurator.
Mergify does not sync branch protection rules. Overall disabling won't hurt because we have the same checks exist in mergify config already and branch protection rules won't even allow direct merge. It is already duplicate rule checking to include branch protection rules in mergify.