docs: document gw new --stack and structural base selection - #44
Merged
Conversation
The skill and README still described `gw new` as always carrying changes onto the branch, with no mention of stacked PRs or the new structural rules. Update both: --stack for stacking on the current branch (with `gh pr create -B`), the feature-branch refusal, and the dirty→HEAD base guarantee. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Follow-up docs for #43. The skill (
.claude/skills/git-workflow/SKILL.md) andREADME.mdstill describedgw newas always carrying changes onto the branch, with no mention of stacked PRs or the new structural base-selection rules.gw new <child> --stack→gh pr create -B <parent>→gw syncas the teardown.newlines + Commands table (added the--stackrow), and added an "Unambiguous base" bullet under Safety Features.Why
Keep the documented workflow in sync with the shipped behavior so the state-driven
gw statusguidance and the skill stay the single source of truth.🤖 Generated with Claude Code