Skip to content

merge queue: queuing main (cb0cafd) and #11822 together#11847

Closed
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/633d845aa7
Closed

merge queue: queuing main (cb0cafd) and #11822 together#11847
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/633d845aa7

Conversation

@mergify

@mergify mergify Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

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

Branch main (cb0cafd) and #11822 are queued together for merge.

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

jd and others added 3 commits June 13, 2026 21:21
Replace the git rebase -i flows in the Updating Stacks guide with the
dedicated non-interactive subcommands the CLI now ships:
edit/reword/reorder/move/drop/fixup/squash, each with --dry-run.

Document the revision-history comment and `mergify stack note`, add a
revision-history section (and browser-extension screenshot) to the
reviewing guide, add the stack-revision-history git config option, and
use `mergify stack sync` after a merge instead of a bare re-push.

Refresh the stack-comment screenshot to the current table layout, fix
stale "interactive rebase" rows in the gh-stack and Graphite comparison
tables, and soften the landing-page claim that there are no new commands
to learn.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I084ff85fe6c9214271eaa9d4bd0d9620777d540a
Add an honest comparison between Mergify Stacks and stacking by hand
with `git rebase` + `gh pr create`, the baseline every other stacking
tool is measured against.

Covers the manual recipe and its upkeep cost, a feature-by-feature
table, a candid "when plain Git is enough" section, where Stacks pulls
ahead (self-maintaining chain, Change-Id identity across rewrites,
reviewer context, Merge Queue integration), an incremental "coming from
a custom script" path, and an explicit off-ramp note. Wire it into the
compare index grid.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I7f58b1226bdb39616cc81de109aa9b5ebfbedcf3
@mergify mergify Bot deployed to Mergify Merge Protections June 16, 2026 07:48 Active
@mergify mergify Bot closed this Jun 16, 2026
@mergify mergify Bot deleted the mergify/merge-queue/633d845aa7 branch June 16, 2026 07:50
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