Skip to content

merge queue: checking #457 on main (94593f3), stacked on #446 - #460

Closed
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/799196c01b
Closed

merge queue: checking #457 on main (94593f3), stacked on #446#460
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/799196c01b

Conversation

@mergify

@mergify mergify Bot commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

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

#457 is queued for merge on branch main (94593f3).

Stacked behind 1 pull request queued ahead of this batch, not part of it. These checks run on a tip that also carries its commits, so a failure here can come from it as much as from #457.

Queued ahead of this batch:

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

Required conditions of queue rule admin-bypass for merge:

  • check-success = lint
  • check-success = test

Required conditions to stay in the queue:

---
checking_base_sha: 178d47973ce4faacb7a5a13e273d7ff0c0892781
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 457
    scopes: []
scopes: []
...

EdbertChan and others added 4 commits September 11, 2026 18:05
A PR that already exists gets one of two treatments, read off its current
diff: stack another commit when its claim still holds and the addition is
small, or overwrite the branch when the diff stopped matching the claim --
it carries work already on the base, it mixes review units, or it ships a
second claim. The record that gets read later is the final diff and body, so
such a branch is rewritten rather than explained in Slice Rationale.

Overwriting requires a backup branch and --force-with-lease; a lease failure
means another session moved the branch, so re-read it instead of forcing. The
choice is mechanical and is not a question for the user.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Gnua5cuAAF1ey1b7zRqJCC
Change-Id: I3839f20ff1f27f9375ec7cf84816e23747986b0a
Five phrase lists under engine/hooks/diu-stop/phrases/ name the kinds of wording that left the user asking what a reply meant: words the assistant made up, raw code or setting names, internal tool names, tech jargon and abbreviations, and status words. Data and one test only; nothing reads them yet.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Gnua5cuAAF1ey1b7zRqJCC
Change-Id: I4860c82b5b8a8a6b84a9397e289c7023fd5d7730
@mergify mergify Bot closed this Sep 12, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/799196c01b branch September 12, 2026 01:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant