Skip to content

docs(agent): required_signatures and deletion rulesets are checked, not ignored - #12409

Merged
mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/health-audit-merge-queue-2
Aug 17, 2026
Merged

docs(agent): required_signatures and deletion rulesets are checked, not ignored#12409
mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/health-audit-merge-queue-2

Conversation

@mergify-ci-bot

Copy link
Copy Markdown
Contributor

The GitHub rulesets page listed required_signatures and deletion among the
rule 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 none injection mode needs a merge_bot_account on the
queue action. That option lives on the queue rule; the action takes only a
name, so the documented config would have been rejected.

The bypass actor section only mentioned exempt. Which mode is enough depends
on what the queue is doing: creating, renaming, pushing to and deleting queue
branches are raw ref operations that pull_requests_only does not cover, while
always is fine for everything except GitHub-native stacks. That section and
the branch name pattern one, which claimed only exempt works, now agree.

On the stacks page, a pull request waiting on its predecessors was said to show
a stack-predecessor-queued condition. No such condition exists; the queue
emits 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-config also
carries no special meaning; making shared files affect every scope is what
barrier_files is for.

The deployment step also named a dashboard entry "Deploy"; it is "Deployment".

@mergify
mergify Bot deployed to Mergify Merge Protections August 17, 2026 10:49 Active
@mergify

mergify Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 6 merge protections satisfied — ready to merge.

Show 6 satisfied protections

🟢 🤖 Continuous Integration

  • all of:
    • check-success = build
    • check-success = lint
    • check-success = test
    • any of:
      • check-success = test-broken-links
      • label = ignore-broken-links
    • any of:
      • -head-repo-full-name~=^Mergifyio/
      • check-success=Cloudflare Pages

🟢 👀 Review Requirements

  • any of:
    • #approved-reviews-by >= 2
    • author = dependabot[bot]
    • all of:
      • -head ~= ^docs-agent/
      • author = mergify-ci-bot

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 🔎 Reviews

  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

🟢 📕 PR description

  • body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

@mergify
mergify Bot requested a review from a team August 17, 2026 10:51
@mergify
mergify Bot requested a review from a team August 17, 2026 13:22
@mergify

mergify Bot commented Aug 17, 2026

Copy link
Copy Markdown
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

@mergify mergify Bot added the queued label Aug 17, 2026
@mergify
mergify Bot merged commit 7e2a192 into Mergifyio:main Aug 17, 2026
9 checks passed
@mergify mergify Bot removed the queued label Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants