--- next_cursor: eyJzY29yZSI6MCwic2VxIjo2MDAsInNpbmNlIjpudWxsLCJ0b29sIjoiZ2gtc3RhY2siLCJ2IjoxfQ has_more: true next: https://sincecutoff.com/v1/changes.md?tool=gh-stack&score=0&cursor=eyJzY29yZSI6MCwic2VxIjo2MDAsInNpbmNlIjpudWxsLCJ0b29sIjoiZ2gtc3RhY2siLCJ2IjoxfQ items: 10 --- # sincecutoff.com changes: gh-stack ## gh stack switch interactively selects a branch in the current stack (gh-stack, 2026-04-20) Published 2026-10-13 - slug: gh-stack-switch-interactively-selects-a-branch-in-the-current-stack-fad9d2f35cab - score: 0.96 How to use it: When you need to switch to a branch in the current stack, run `gh stack switch` in an interactive terminal and select the branch from the ordered picker. Examples: ``` gh stack switch ``` - why_it_matters: Interactively switch to a branch in the current stack. - sources: , , - gotchas: "Version: v0.0.2"; "Prerequisite: Requires an interactive terminal."; "Prerequisite: Install the extension with `gh extension install github/gh-stack`; requires GitHub CLI `gh` v2.0 or later."; "Interactive picker command." ## gh-stack gh stack modify restructures a branch stack (gh-stack, 2026-05-11) Published 2026-10-13 - slug: gh-stack-gh-stack-modify-restructures-a-branch-stack-996d4c53c39b - score: 0.96 How to use it: When you have an active stack checked out, a clean working tree, no rebase in progress, no PR queued to merge, and linear history, run `gh stack modify` to open the TUI and stage branch changes. Save to apply them; if a conflict occurs, resolve it and run `gh stack modify --continue`, or restore the pre-modify state with `gh stack modify --abort`. Examples: ``` gh stack modify ``` ``` gh stack modify --continue ``` ``` gh stack modify --abort ``` - why_it_matters: Restructure a branch stack by dropping, folding, renaming, or reordering branches. - sources: , , - gotchas: "Version: v0.0.3"; "--continue: Continue after resolving conflicts."; "--abort: Abort the modify session and restore the stack to its pre-modify state."; "x: Drop a branch and its commits from the stack."; "d: Fold the selected branch into the branch below it, toward trunk."; "u: Fold the selected branch into the branch above it, away from trunk."; "r: Rename a branch locally and in stack metadata."; "Shift+↓ / Shift+↑: Move a branch down toward trunk or up away from trunk."; "Ctrl+S: Apply staged changes."; "Prerequisite: Requires an active stack checked out locally, a clean working tree, no rebase in progress, no PR in the stack queued for merge, and linear commit history."; "Prerequisite: Install GitHub CLI 2.0 or later and Git 2.36 or later; install the extension with `gh extension install github/gh-stack`. Authenticate with `gh auth login` if needed."; "Prerequisite: The release notes state Stacked PRs must be enabled for the repository for the CLI functionality to work."; "The command is interactive." ## gh-stack init adopts multiple branches and derives their prefix (gh-stack, 2026-05-15) Published 2026-10-13 - slug: gh-stack-init-adopts-multiple-branches-and-derives-their-prefix-1450b30dea80 - score: 0.90 How to use it: When initializing a stack from multiple existing branches, run `gh stack init ...`; existing branches are adopted automatically and v0.0.4 derives the prefix from their names. Examples: ``` gh stack init ``` - why_it_matters: Initialize a stack from multiple existing branches with a shared prefix. - sources: , - gotchas: "Version: v0.0.4"; "branches... (required): One or more branch names, processed in order; existing branches are adopted automatically. For this task, supply multiple names."; "--adopt: Deprecated, hidden, but still accepted; existing branches no longer require it to be adopted."; "Prerequisite: Install the extension with `gh extension install github/gh-stack`; the README says GitHub CLI (`gh`) must be installed first."; "The `--adopt` flag is deprecated and hidden but still accepted."; "Docs conflict: Later official docs say automatic prefix detection was removed; branch names with slashes are taken literally. That behavior is newer than v0.0.4 and does not apply to this card's version: https://github.com/github/gh-stack/releases." ## gh-stack sync --prune deletes merged-PR refs during sync (gh-stack, 2026-05-15) Published 2026-10-13 - slug: gh-stack-sync-prune-deletes-merged-pr-refs-during-sync-ec7e15ba10cc - score: 0.94 How to use it: When syncing a stack with merged PRs, run `gh stack sync --prune` to automatically delete their local branches. The documentation does not confirm deletion of remote-tracking refs. Examples: ``` gh stack sync --prune ``` - why_it_matters: During sync, remove local branches and remote-tracking refs for merged pull requests. - sources: , - gotchas: "Version: v0.0.4"; "--prune: Automatically delete local branches for merged PRs during sync."; "Prerequisite: Install the GitHub CLI extension with `gh extension install github/gh-stack`; the docs require GitHub CLI v2.0+ and Git 2.36+."; "Docs conflict: The release note says pruning deletes local branches and remote-tracking refs. The command documentation describes deletion of local branches only and does not confirm remote-tracking ref deletion." ## gh stack modify inserts empty branches (gh-stack, 2026-05-26) Published 2026-10-13 - slug: gh-stack-modify-inserts-empty-branches-f8ea69991bea - score: 0.94 How to use it: When restructuring a stack, run `gh stack modify`; in its TUI press `i` to stage an empty branch below the cursor or `I` to stage one above, then press `Ctrl+S` to apply the staged changes. [v0.0.5 README](https://github.com/github/gh-stack/blob/v0.0.5/README.md#L388-L424) Examples: ``` gh stack modify ``` - why_it_matters: Insert an empty branch above or below a branch while restructuring a stack. - sources: , , , , , - gotchas: "Version: v0.0.5"; "i: Stage insertion of an empty branch below the cursor."; "I: Stage insertion of an empty branch above the cursor."; "Ctrl+S (required): Apply all staged changes."; "Prerequisite: Requires an active local stack, a clean working tree, no rebase in progress, no stack PR queued for merge, and linear commit history."; "Prerequisite: Requires GitHub CLI (`gh`) v2.0+ and installation of the extension with `gh extension install github/gh-stack`." ## gh stack rebase adds --no-trunk (gh-stack, 2026-06-15) Published 2026-10-13 - slug: gh-stack-rebase-adds-no-trunk-0fb30cb2dc67 - score: 0.94 How to use it: When you need to align stack branches without fetching or rebasing trunk, run `gh stack rebase --no-trunk`. Examples: ``` gh stack rebase --no-trunk ``` - why_it_matters: Rebase the branches in a stack without network access. - sources: , - gotchas: "Version: v0.0.6"; "--no-trunk: Skip trunk; rebase stack branches onto each other with no fetch or trunk rebase."; "Runs only the inter-branch cascade rebase; skips all remote fetch and trunk operations." ## gh stack submit TUI customizes a whole stack (gh-stack, 2026-06-30) Published 2026-10-13 - slug: gh-stack-submit-tui-customizes-a-whole-stack-e5fc2aba50b3 - score: 0.96 How to use it: When preparing PRs for a stack, run `gh stack submit` in an interactive terminal to choose branches, edit each PR’s title and description, and set ready or draft state. Submit the choices together with Ctrl+S. Examples: ``` gh stack submit ``` - why_it_matters: Before creating PRs for a stack, customize which branches become PRs and each PR’s details. - before: Previously, submit could only customize each PR’s title. - sources: , - gotchas: "Version: v0.0.7"; "branch selection (Ctrl+X): Deselect a branch; deselecting it also deselects branches above it. Re-including a branch re-includes branches below it. Branches without PRs are included by default."; "PR title: Edit each PR’s title in the editor."; "PR description: Edit each PR’s description; the editor provides markdown preview and a `$EDITOR` escape."; "ready/draft toggle: Choose ready for review or draft for each PR. New PRs default to ready for review in the editor."; "Ctrl+S (required): Submit the edited PRs together."; "Prerequisite: Install the extension with `gh extension install github/gh-stack`; requires GitHub CLI (`gh`) v2.0+."; "Prerequisite: Stacked PRs is in private preview; the feature must be enabled for the repository."; "Prerequisite: Run in an interactive terminal to open the editor."; "The interface is keyboard- and mouse-driven." ## gh-stack branch names no longer use stack prefixes or numbered naming (gh-stack, 2026-07-15) Published 2026-10-13 - slug: gh-stack-branch-names-no-longer-use-stack-prefixes-or-numbered-naming-98eee258a6ae - score: 0.94 How to use it: When adding a named branch, use its name directly; `gh stack add refactor/foo` creates that branch. To create a branch from a message, run `gh stack add -m ""`; the v0.0.8 release says an omitted name generates `MM-DD-slug`. Examples: ``` gh stack add refactor/foo ``` ``` gh stack add -m "" ``` - why_it_matters: When adding a branch with a chosen name or generating one from a message, use the branch name directly or the new generated-name form. - before: Use the stack branch-name prefix or coupled numbered naming; `init` accepts `-p/--prefix` and `-n/--numbered`. - sources: , - gotchas: "Version: v0.0.8"; "branch: Optional branch name; if omitted, `add` prompts for one, or auto-generates one when `-m` is provided."; "-m, --message : Create a commit with this message before creating the branch; with no branch name, generates the branch name."; "-A, --all: Stage all changes, including untracked files; requires `-m`."; "-u, --update: Stage changes to tracked files only; requires `-m`."; "Prerequisite: Install the extension with `gh extension install github/gh-stack`; requires GitHub CLI (`gh`) v2.0 or later."; "Prerequisite: For an existing stack, run `add` while on its topmost branch."; "Existing stack files carrying `prefix`/`numbered` keys still load; the fields are ignored and dropped on the next save."; "Docs conflict: The current README is newer than v0.0.8 and gives an auto-generated-name example `03-24-auth_middleware`; the release states the v0.0.8 form is `MM-DD-slug`."; "Docs conflict: The current README documents only `-b, --base ` for `init` and omits the removed `-p/--prefix` and `-n/--numbered` flags; it does not document legacy `prefix`/`numbered` file handling." ## gh stack checkout opens an interactive stack picker (gh-stack, 2026-07-15) Published 2026-10-13 - slug: gh-stack-checkout-opens-an-interactive-stack-picker-76fc5f8b58f0 - score: 0.96 How to use it: When you need to choose a stack without knowing its identifier, run `gh stack checkout` in an interactive terminal and select it from the picker. Use the All/Local/Remote tabs or `/` search; selecting a remote-only stack clones it locally before switching to it. Examples: ``` gh stack checkout ``` - why_it_matters: When choosing a local or GitHub stack without already knowing its identifier, run `gh stack checkout` with no argument and select the desired stack. - sources: , - gotchas: "Version: v0.0.8"; "stack-number, pr-number, pr-url, branch: Optional checkout target; omitting it opens the picker in an interactive terminal."; "All / Local / Remote tabs: Filter the picker by all available stacks, locally tracked stacks, or remote stacks."; "/: Start searching the picker; the v0.0.8 release says search matches the stack number, base, and every stack branch, including mid-stack branches."; "Prerequisite: The picker opens when run without arguments in an interactive terminal."; "Prerequisite: Install the extension with `gh extension install github/gh-stack`; requires GitHub CLI `gh` v2.0+. Stacked PRs must be enabled for the repository."; "The picker searches stack number, base branch, and every branch in the stack, including mid-stack branches." ## gh-stack commands reference stacks by number (gh-stack, 2026-07-15) Published 2026-10-13 - slug: gh-stack-commands-reference-stacks-by-number-a284b3dc9565 - score: 0.92 How to use it: When checking out or unstacking a tracked stack by its GitHub UI number, use that number: run `gh stack checkout ` to check it out or `gh stack unstack ` to unstack it. Find the number in the GitHub UI or gh-stack output. Examples: ``` gh stack checkout ``` ``` gh stack unstack ``` - why_it_matters: When checking out or unstacking a tracked stack by its GitHub stack UI identifier, use its stack number. - sources: , - gotchas: "Version: v0.0.8"; " (checkout): A stack number; checkout also accepts a PR number, PR URL, or branch. A bare number is matched as a stack or PR number before being tried as a branch name."; " (unstack): The GitHub UI stack number; targets that stack from anywhere in the repository. If omitted, targets the active stack."; "Prerequisite: Install the extension with `gh extension install github/gh-stack`; requires GitHub CLI (`gh`) v2.0+."; "Prerequisite: Stacked PRs must be enabled for the repository. Authenticate with GitHub CLI to run stack operations." Next: https://sincecutoff.com/v1/changes.md?tool=gh-stack&score=0&cursor=eyJzY29yZSI6MCwic2VxIjo2MDAsInNpbmNlIjpudWxsLCJ0b29sIjoiZ2gtc3RhY2siLCJ2IjoxfQ Save `next_cursor`; next visit, pass it to get only what was published since.