Skip to content

merge queue: checking #12770 on main (c20b99c), stacked on #12769 and #12764 - #12787

Closed
mergify[bot] wants to merge 6 commits into
mainfrom
mergify/merge-queue/3c717a2e3f
Closed

merge queue: checking #12770 on main (c20b99c), stacked on #12769 and #12764#12787
mergify[bot] wants to merge 6 commits into
mainfrom
mergify/merge-queue/3c717a2e3f

Conversation

@mergify

@mergify mergify Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

#12770 is queued for merge on branch main (c20b99c).

Stacked behind 2 pull requests queued ahead of this batch, not part of it. These checks run on a tip that also carries their commits, so a failure here can come from them as much as from #12770.

Queued ahead of this batch:

This pull request has been created by Mergify to speculatively check the mergeability of #12770.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 9017adfaa73656802c58d9f1f7c94316daffe88e
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12770
    scopes: []
scopes: []
...

mergify-ci-bot and others added 6 commits September 10, 2026 04:24
Review Requirements' DefaultReviewCond anchor required
#approved-reviews-by >= 2; drop it to 1 so a single approval is
enough to merge on Mergifyio/docs, for everyone, not another
carve-out.

DefaultReviewCond is shared by the Hotfix Review Requirements
protection (`or: *DefaultReviewCond`) and by the request-review
pull request rule, so both move with it. That also makes the
hotfix-specific hotfix Review Requirements' escapes dead: its
eng-mgr-with-one-approval and devs-with-eng-mgr-or-fix/revert-title
branches only ever granted "one approval clears review", which the
new default already grants to any author. Removed them along with
the now-redundant `label != hotfix` guard in the request-review
rule's condition, which existed only to avoid double-counting that
escape.

Checked the repo's GitHub side: of its 9 rulesets, only "Require
pull request for default branch" carries a pull_request rule, and
its required_approving_review_count is 0 — no ruleset conflicts
with the new threshold.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Change-Id: I9983de27602a153f5510b61cc8bb5c91a86e7705
docs#12728 dropped the real-invoice billing example from billing.mdx —
both <Image> uses and both import lines — and left
invoice-previous-period.png and invoice-next-period.png behind with
nothing pointing at them.

A repo-wide sweep for the same pattern (path-relative-to-images/, not
basename — see the next commit) turned up five more:
merge-protections/freeze-main.png and stacked-gh-pr.png /
stacked-mergify-pr.png were never wired into the pages they were added
for, and workflow/writing-your-first-rule/{summary,config-editor}.png
belonged to a page removed wholesale in 068ac36.

Deleting first, before the check that follows, so that check is never
red on main.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Change-Id: I770291bedc49acb609264a58b7032c9fad738c58
@mergify
mergify Bot deployed to Mergify Merge Protections September 11, 2026 12:37 Active
@mergify mergify Bot closed this Sep 11, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/3c717a2e3f branch September 11, 2026 12:40
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.

2 participants