Skip to content

merge queue: embarking main (b314393), #1266 and #1268 together#1284

Closed
mergify[bot] wants to merge 4 commits intomainfrom
mergify/merge-queue/d9892bab41
Closed

merge queue: embarking main (b314393), #1266 and #1268 together#1284
mergify[bot] wants to merge 4 commits intomainfrom
mergify/merge-queue/d9892bab41

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Apr 21, 2026

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

Branch main (b314393), #1266 and #1268 are embarked together for merge.

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

jd and others added 4 commits April 21, 2026 10:53
Add "mergify stack squash SRC... into TARGET [-m MESSAGE]" which reorders
SRC commits adjacent to TARGET and folds them in without opening an
editor. Without -m, TARGET's message is kept (via the fixup rebase
action). With -m, the rebase inserts an `exec git commit --amend -m ...`
line right after the last fixup source, which runs while HEAD still
points at the combined target — so prepare-commit-msg re-attaches the
Change-Id normally.

Errors when SRC == TARGET, when a SRC is duplicated, or when a SRC or
TARGET prefix is unknown. Supports --dry-run.

Click does not allow two positionals when one is variadic, so the CLI
takes a single tokens tuple and parses "SRC... into TARGET" manually
(_parse_squash_tokens); parser edge cases are covered by unit tests.

Also documents the squash command in skills/mergify-stack/SKILL.md.

Change-Id: I558e6e6f5e33252ad52f8e4a002dfc0141d693b0
Complete the stack-notes feature: fetch refs/notes/mergify from the
remote before planning, read the note attached to each updated commit
into LocalChange.reason, and push the ref atomically alongside the
stack branches with --force-with-lease.

The revision-history PR comment gains a new "Reason" column:

  | # | Type | Changes | Reason | Date |

The parser accepts both the legacy 4-column format and the new 5-column
format, preserving legacy rows verbatim so old comments aren't rewritten.

Reason cells escape pipes and newlines for markdown-table safety and
truncate at 200 characters. Error catches for the notes fetch and the
per-commit notes read are narrowed to the specific "ref/note not found"
cases so other failures (auth, network, corruption) still surface.

Depends-On: the preceding 'stack note' command PR.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Change-Id: I59af53609d8f0875b000f82cae085368adb5d5ab
@mergify mergify Bot deployed to Mergify Merge Protections April 21, 2026 13:18 Active
@mergify mergify Bot closed this Apr 21, 2026
@mergify mergify Bot deleted the mergify/merge-queue/d9892bab41 branch April 21, 2026 13:24
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