-
Notifications
You must be signed in to change notification settings - Fork 238
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
Repository settings guidelines: Apply rules also to branch creation #2178
Conversation
Wouldn't it prevent dependabot and similar tools from working? They push PRs from branches they create on the target repo, from what I remember. |
If you're using dependabot you can make a branch protection rule for its branches specifically. |
Sounds good. As long as we are not breaking current tools with this change, I'm fine with the change. |
@jpkrohling exactly as @austinlparker said - the rules for Dependabot and Renovate overrule the community/docs/how-to-configure-new-repository.md Lines 98 to 117 in 3f4b528
|
@arminru can you create an issue to apply this to all repos and link it here? |
@danielgblanco Done! #2213 |
This setting enables the branch protection rule to not only cover PRs targeting an existing branch, but also the creation of new branches.
For the
main
branch, this doesn't make a difference as it will usually be there, but for the**/**
pattern, as percommunity/docs/how-to-configure-new-repository.md
Lines 119 to 121 in 8e17c30
main
are re-used.Docs:
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule