Repository navigation
Conversation
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
This isn't open to contributors yet, so I'm going to close this out. We haven't had time to do a proper assessment and we don't know whether it's something we need to fix internally, or how many articles are affected and what the scope of the fix will be. Sorry this won't have been the outcome you were hoping for, and please keep an eye out for issues marked |
Why:
The ruleset documentation explains how the
Restrict creationsrule works, but it does not mention that merge queue branches also need permission to be created.When this rule applies to all branches, merge queue branches matching
gh-readonly-queue/{base_branch}can be blocked unless the GitHub Merge Queue app is added to the bypass list.Closes #45334
What's being changed:
Add documentation explaining that the GitHub Merge Queue app must be added to the bypass list when the
Restrict creationsrule applies to merge queue branches.Testing:
git diff --check.