We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 50 since January 2026, each linked to its source.
ghWhen a stack’s branches are spread across worktrees, use `gh stack rebase`, `gh stack sync`, or `gh stack modify`; gh-stack runs each change in the worktree owning its branch. If a rebase or modify pauses for conflicts, resolve and stage them in the reported checkout, then continue or abort from any worktree.
gh stack rebaseFor severity triage or a withdrawn-advisory audit, call `securityAdvisories` with the relevant `severities` or `isWithdrawn` filter and select the advisory fields you need.
gh api graphql -F 'severities[]=HIGH' -f query='query($severities: [SecurityAdvisorySeverity!]) { securityAdvisories(severities: $severities, first: 100) { nodes { ghsaId severity summary } } }'For individual or stacked PRs, submit a merge request with `PUT`; poll the result with `GET` using the returned UUID. Set `merge_action` for direct or queued merges, and set `bypass_rules` only when authorized.
curl -L -X PUT -H "Accept: application/vnd.github+json" -H "Authorization: Bearer <TOKEN>" -H "X-GitHub-Api-Version: 2026-03-10" "https://api.github.com/repos/<OWNER>/<REPO>/pulls/<PULL_NUMBER>/merge-async" -d '{"merge_action":"default"}'When `gh stack add` runs interactively on a branch outside a stack, accept its offer to initialize a stack; the supplied or generated branch name becomes the first layer.
gh stack add [branch]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 checkoutWhen you need to start issue work in a separate Git working copy, run `gh issue develop` with `--checkout` and `--worktree` to create and check out the linked branch there. The documented example uses issue 123 and `/path/to/wt-feature`.
gh issue develop 123 --checkout --worktree /path/to/wt-featureWhen creating or editing an issue or pull request, or adding a comment, use repeatable `--attach <file>` to upload local images or videos and add them to the body. Include optional image alt text after `#`; an existing body reference to the file is rewritten to the uploaded asset URL, otherwise the attachment is appended.
gh issue create --attach './repro.png#The error state'When checking out a pull request into a separate Git worktree, use `gh pr checkout` with `--worktree <path>`.
gh pr checkout 12 --worktree ../wt-featureWhen searching issues by meaning, use `--search-type semantic`; to combine keyword and semantic ranking, use `--search-type hybrid`.
gh search issues "<natural-language query>" --search-type semanticWhen editing a GitHub project item by field and single-select option name, run `gh project item-edit` with the project number, owner, item URL, field name, and option name.
gh project item-edit <project-number> --owner <owner> --url <issue-or-pull-request-url> --field "Status" --value "In Progress"