Skip to content

merge queue: checking #12719 on main (31527bf) - #12752

Closed
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/1957e5d084
Closed

merge queue: checking #12719 on main (31527bf)#12752
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/1957e5d084

Conversation

@mergify

@mergify mergify Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

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

#12719 is queued for merge on branch main (31527bf).

This pull request has been created by Mergify to check the mergeability of #12719.
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: 31527bfa427e0baa59c648a4d2b9920c2370eb36
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12719
    scopes: []
scopes: []
...

jd and others added 4 commits September 8, 2026 14:38
The Pull Request Dependencies section said a `Depends-On:` header could point
at "other repositories with Mergify installed within your organization". The
constraint is the same repository *owner*, which may be a user account rather
than an organization. A reference to another owner is rendered with a
"depends-on conditions must have the same repository owner" warning and never
satisfies.

The section was also silent on what happens to a reference Mergify cannot
resolve — another owner, a repository without Mergify, or a pull request that
does not exist. None of those ever reach the `depends-on` attribute, so the
condition stays unsatisfied and blocks the merge rather than being skipped,
which is the behaviour a reader most needs to be told about.

This brings the page in line with the same rules already documented for the
`depends-on` merge protection in /merge-protections/builtin, which was
corrected and left this page behind.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019V4gXwb2UucysW4xmB7bAw
Change-Id: I790b2c0c6e38ed5eff9ac587378765c72939f264
…ount

The caution scoped the deprecation to the `rebase` action "with `bot_account`"
on fork pull requests. Rebasing always impersonates a GitHub user: when
`bot_account` is unset Mergify falls back to the pull request author (or the
command sender), and refuses to run when neither resolves. The deprecation
notice is posted on any fork rebase, so a reader whose configuration sets no
`bot_account` read the caution as not applying to them when it does — the one
group the callout most needed to reach.

The page's only example was also built on `autosquash`, which the schema marks
deprecated, so the single worked example on the page taught the option we are
steering people away from. Replaced with a plain label-triggered rebase,
matching the "Squash on Label" example on the squash page.

Nothing is lost by dropping `autosquash` from the example: the Parameters
table still renders its `deprecated` badge from the schema, and Rebase
Requirements still documents its effect on the `#commits > 1` disjunct.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019V4gXwb2UucysW4xmB7bAw
Change-Id: Ibf1f715b72dbd21e819305a61b27555cf62874c7
The page documented the parameters and nothing about when a review is posted,
which is where the surprises are. Four behaviours are load-bearing and were
undocumented:

- A review whose type and body match one Mergify already posted is skipped,
  unless it has posted the opposite type since. So a rule that re-approves on
  every push posts once, not once per push.
- That comparison is per account, so changing `bot_account` re-posts an
  otherwise identical review under the new one.
- On a merged pull request only `COMMENT` is posted; `APPROVE` and
  `REQUEST_CHANGES` are ignored and reported as a success, so a green check is
  not proof the review landed.
- A `REQUEST_CHANGES` or `COMMENT` with no `message` is posted with a generated
  default body rather than an empty one.

This is the last of the three corrections Mergifyio/ci-bot#442 collects; the
other two are the commits below it in this stack, so the issue closes once the
whole stack has landed.

Fixes Mergifyio/ci-bot#442

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019V4gXwb2UucysW4xmB7bAw
Change-Id: Ieb0af482a6b6c0934a9322c3e9d0b2c0fe005479
@mergify
mergify Bot deployed to Mergify Merge Protections September 9, 2026 11:29 Active
@mergify mergify Bot closed this Sep 9, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/1957e5d084 branch September 9, 2026 11:31
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.

1 participant