docs(stacks): add "vs Plain Git" comparison page#11822
Merged
mergify[bot] merged 2 commits intoJun 16, 2026
Merged
Conversation
Member
Author
|
This pull request is part of a Mergify stack:
|
Contributor
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 ⛓️ Depends-On RequirementsWonderful, this rule succeeded.Requirement based on the presence of
🟢 🤖 Continuous IntegrationWonderful, this rule succeeded.
🟢 👀 Review RequirementsWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 ReviewsWonderful, this rule succeeded.
🟢 📕 PR descriptionWonderful, this rule succeeded.
|
jd
commented
Jun 12, 2026
jd
force-pushed
the
devs/jd/worktree-update-stacks/sync-stacks-docs-current-cli--084ff85f
branch
from
95102a3 to
4a7c17e
Compare
jd
force-pushed
the
devs/jd/worktree-update-stacks/add-vs-plain-git-comparison-page--7f58b122
branch
from
1696ea1 to
ce4c04e
Compare
Member
Author
Revision history
|
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
jd
force-pushed
the
devs/jd/worktree-update-stacks/add-vs-plain-git-comparison-page--7f58b122
branch
from
ce4c04e to
9cb8af6
Compare
jd
force-pushed
the
devs/jd/worktree-update-stacks/sync-stacks-docs-current-cli--084ff85f
branch
from
4a7c17e to
671150e
Compare
Base automatically changed from
devs/jd/worktree-update-stacks/sync-stacks-docs-current-cli--084ff85f
to
main
June 16, 2026 07:03
JulianMaurin
approved these changes
Jun 16, 2026
remyduthu
approved these changes
Jun 16, 2026
kozlek
approved these changes
Jun 16, 2026
Contributor
|
Queued — the merge queue status continues in this comment ↓. |
Contributor
Merge Queue Status
This pull request spent 3 minutes 33 seconds in the queue, including 2 minutes 3 seconds running CI. Required conditions to merge
|
53 tasks
mergify
Bot
deleted the
devs/jd/worktree-update-stacks/add-vs-plain-git-comparison-page--7f58b122
branch
53 tasks
mergify Bot
pushed a commit
that referenced
this pull request
Jun 16, 2026
The browser extension now surfaces Stacks context (the stack chain and revision-history timeline) in addition to merge queue controls, so nesting it under Merge Queue no longer fits. Relocate the page to /browser-extensions and group it with the CLI under a new top-level Tools nav group, move its images alongside it, broaden the content with a Stacks panel section, repoint the inbound links from the stacks docs, and add a 301 redirect from the old URL. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Depends-On: #11822
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add an honest comparison between Mergify Stacks and stacking by hand
with
git rebase+gh pr create, the baseline every other stackingtool 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
Depends-On: #11820