docs(stacks): add "vs Plain Git" comparison page#11822
Open
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. 🔴 👀 Review RequirementsWaiting for
This rule is failing.
🔴 🔎 ReviewsWaiting for
This rule is failing.
🟢 ⛓️ Depends-On RequirementsWonderful, this rule succeeded.Requirement based on the presence of
🟢 🤖 Continuous IntegrationWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 📕 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
|
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
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
1 participant
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