sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

gh stack checkout resolves active remote stacks

Introduced 2026-09-02 · score 0.96

HOW TO USE IT

If the current branch or requested branch is not tracked locally but belongs to an active remote stack, run `gh stack checkout` or `gh stack checkout <branch>` and accept the prompt to check it out. The command imports the matching stack through the PR checkout flow; fully merged stacks are omitted. ([v0.1.1 release](https://github.com/github/gh-stack/releases/tag/v0.1.1))

gh stack checkout
gh stack checkout <branch>

WHY THIS HELPS

Check out a stack when the current branch or a requested branch belongs to an active GitHub stack but is not in a local stack or tracked locally.

BEFORE THIS CHANGE

For a branch not tracked locally or not part of a local stack, use the existing checkout behavior if remote resolution does not offer a match.

REQUIREMENTS AND LIMITATIONS

  • Version: v0.1.1
  • [<branch>]: Optional branch name to check out; when supplied and not tracked locally, the command searches remote stacks for a match. With no argument, it checks whether the current branch belongs to an active remote stack. ([gh-stack README](https://github.com/github/gh-stack/blob/v0.1.1/README.md))
  • Prerequisite: Install the GitHub CLI extension with `gh extension install github/gh-stack`. ([v0.1.1 release](https://github.com/github/gh-stack/releases/tag/v0.1.1))
  • Prerequisite: The command’s no-argument remote detection is offered in an interactive terminal. ([gh-stack README](https://github.com/github/gh-stack/blob/v0.1.1/README.md))
  • Resolution is best-effort: network failures, no or multiple matches, or a declined prompt fall through to existing behavior.
  • Fully merged stacks are ignored.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card