GH-ISSUE-DEVELOP(1)
β¨ NAME β¨
ok so this is gh-issue-develop β the GitHub CLI manual page for it, bestie β and it's literally all about managing linked branches for an issue π
πΈ SYNOPSIS πΈ
gh issue develop {<number> | <url>} [flags]
so you either hit it with an issue number or a URL, and then sprinkle flags on top. that's the whole vibe check π¦
π DESCRIPTION π
Manage linked branches for an issue. that's it, that's the girlboss job π
now the important part, so listen up π«Ά β when you use the --base flag, the new development branch gets created from the specified remote branch. and that new branch? it gets configured as the base branch for pull requests you create using gh pr create. so like, it's not just some random branch floating around, it's got main character energy in your PR flow β¨
π OPTIONS π
-b,--base<string>β the name of the remote branch you want your shiny new branch to be created from π±--branch-repo<string>β the name or URL of the repository where you want your new branch to live π-c,--checkoutβ checks out the branch after it's created, so you're instantly on it, no cap β¨-l,--listβ lists the linked branches for the issue. very "let me see what we're working with" of you π-n,--name<string>β the name of the branch to create π·οΈ--worktree<path>β checks out the branch into a worktree at the given path. yes, a worktree. fancy fr fr π³
π¦ OPTIONS INHERITED FROM PARENT COMMANDS π¦
-R,--repo[HOST/]OWNER/REPOβ select another repository using the[HOST/]OWNER/REPOformat. gotta know which repo you're in, iykyk π
β EXIT CODES β
0β Successful execution π1β Error π2β Command canceled π4β Authentication required π
NOTE: specific commands may have additional exit codes. refer to the command's help for more information, bestie π
π EXAMPLE π
# List branches for issue 123
$ gh issue develop --list 123
# List branches for issue 123 in repo cli/cli
$ gh issue develop --list --repo cli/cli 123
# Create a branch for issue 123 based on the my-feature branch
$ gh issue develop 123 --base my-feature
# Create a branch for issue 123 and check it out
$ gh issue develop 123 --checkout
# Create a branch for issue 123 and check it out in a worktree
$ gh issue develop 123 --checkout --worktree /path/to/wt-feature
# Create a branch in repo monalisa/cli for issue 123 in repo cli/cli
$ gh issue develop 123 --repo cli/cli --branch-repo monalisa/cli
π§ SEE ALSO π§
gh-issue(1)β go read that one too, it's giving parent command π
that's the whole page, bestie π this was GitHub CLI v2.102.0, dated Oct 2026 β go forth and link those branches, you're literally gonna slay πΈπ«Ά
π¦ where this page comes from
- opensuse-leap 16.0: gh 2.102.0-bp160.1.1 Β· MIT
- opensuse-leap 16.0: gh 2.102.0-bp160.1.1 Β· MIT
- opensuse-leap 16.0: gh 2.102.0-bp160.1.1 Β· MIT
- opensuse-leap 16.0: gh 2.102.0-bp160.1.1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms