You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: agent skill does not cover --accept-base-change for sync/rebase #640
The agent skill shipped in v0.3.0 (skills/gh-stack) does not mention the new --accept-base-change flag. Its "Non-interactive use" table lists the flags an agent must always pass so a command never opens a prompt, but gh stack sync and gh stack rebase now ask for confirmation when GitHub retargeted the stack after its base branch was deleted and the old base did not merge (gh stack sync --help: "Removing commits from an old base that did not merge requires confirmation, or --accept-base-change"). An agent following the skill under a PTY can reach that confirmation with no guidance.
Additional context: skills/gh-stack/SKILL.md at tag v0.3.0 still says version: "0.2.0" in its frontmatter.
Affected command
gh stack sync, gh stack rebase (agent skill docs)
gh-stack version
gh stack version 0.3.0
GitHub CLI version
gh version 2.105.0 (2026-11-18)
Operating system
Arch Linux, kernel 6.18.64-1-lts
Shell
zsh
Steps to reproduce
Fetch the skill at the release tag: gh api "repos/github/gh-stack/contents/skills/gh-stack/SKILL.md?ref=v0.3.0" -q .content | base64 -d > SKILL.md (same for references/*.md)
The skill tells agents when to pass --accept-base-change (or how to detect a retargeted base) for sync and rebase, ideally as a row in the "Non-interactive use" table and in references/commands.md/troubleshooting.md, with the caution that it drops commits from an old base that never merged. The frontmatter version matches the release.
Actual behavior
No mention of the flag or the retarget confirmation anywhere in the skill; the frontmatter version is stale.
Terminal output
$ grep -rn "accept-base-change" skills/gh-stack
$ gh stack sync --help | grep -n base-change
did not merge requires confirmation, or --accept-base-change.
--accept-base-change Rebase onto a retargeted base even if the old base did not merge
Preflight checks
I searched the existing issues for duplicates.
I ran gh extension upgrade stack and reproduced this issue on the latest stable release.
Activity