gh-stack branch names no longer use stack prefixes or numbered naming
Introduced 2026-07-15 · 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 "<message>"`; the v0.0.8 release says an omitted name generates `MM-DD-slug`.
gh stack add refactor/foogh stack add -m "<message>"WHY THIS HELPS
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 THIS CHANGE
Use the stack branch-name prefix or coupled numbered naming; `init` accepts `-p/--prefix` and `-n/--numbered`.
REQUIREMENTS AND LIMITATIONS
- Version: v0.0.8
- branch: Optional branch name; if omitted, `add` prompts for one, or auto-generates one when `-m` is provided.
- -m, --message <string>: 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 <branch>` for `init` and omits the removed `-p/--prefix` and `-n/--numbered` flags; it does not document legacy `prefix`/`numbered` file handling.
FIRST-PARTY EVIDENCE
Check the installed version and the source before using it. Entry JSON