docs(agent): required_signatures and deletion rulesets are checked, not ignored - #12409
Merged
mergify[bot] merged 1 commit intoAug 17, 2026
Conversation
Contributor
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
jd
approved these changes
Aug 17, 2026
JulianMaurin
approved these changes
Aug 17, 2026
Contributor
Merge Queue Status
This pull request spent 4 minutes 33 seconds in the queue, including 3 minutes 52 seconds running CI. Required conditions to merge
|
60 tasks
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
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.
The GitHub rulesets page listed
required_signaturesanddeletionamong therule types Mergify neither injects nor validates. Both are in fact checked
before the queue touches a branch: a signature rule covering the queue branch
rejects the push, because the merge commits the queue composes locally are
unsigned, and a deletion rule stops the queue from removing the branch before
recreating it. Anyone blocked by one of these was being told the rule had no
effect. They now appear in the compatibility table with a section explaining
both failures and how to resolve them.
The same page said the
noneinjection mode needs amerge_bot_accounton thequeueaction. That option lives on the queue rule; the action takes only aname, so the documented config would have been rejected.The bypass actor section only mentioned
exempt. Which mode is enough dependson what the queue is doing: creating, renaming, pushing to and deleting queue
branches are raw ref operations that
pull_requests_onlydoes not cover, whilealwaysis fine for everything except GitHub-native stacks. That section andthe branch name pattern one, which claimed only
exemptworks, now agree.On the stacks page, a pull request waiting on its predecessors was said to show
a
stack-predecessor-queuedcondition. No such condition exists; the queueemits one
depends-on=condition per predecessor, tagged[stack].On the file-pattern scopes page, two batching claims did not match how batches
are assembled. Overlapping scopes are a ranking preference when filling a
batch, not a guarantee, and parallel mode groups pull requests by their exact
set of scopes, so a change scoped to one project and a change scoped to that
project plus another do not batch together. A scope named
shared-configalsocarries no special meaning; making shared files affect every scope is what
barrier_filesis for.The deployment step also named a dashboard entry "Deploy"; it is "Deployment".