GH-PROJECT(1)

πŸŽ€ gh-project β€” your GitHub Projects bestie πŸŽ€

So this is the gh-project page from the GitHub CLI manual (yes, that manual, the GitHub CLI one πŸ’…). Sit down, grab a strawberry drink πŸ“, and let's get into it.


✨ NAME ✨

gh-project β€” work with GitHub Projects. That's the whole vibe.


🌸 SYNOPSIS 🌸

gh project <command> [flags]

πŸ¦‹ DESCRIPTION πŸ¦‹

Work with GitHub Projects. Iconic. No notes. πŸ‘‘

Okay so the important bit: the minimum required scope for your token is project. Literally the floor. You can verify your token scope by running gh auth status, and you add the project scope by running gh auth refresh -s project. Do that. Don't skip it. πŸ™ˆ


πŸ’– AVAILABLE COMMANDS πŸ’–

Like, there are so many of them. Full roster, no cuts:

That's nineteen. Counted them. Obsessed. 🫢


🧚 EXIT CODES 🧚

So when the command finishes, here's what the numbers mean:

  • 0 β€” successful execution (slay ✨)
  • 1 β€” error 😭
  • 2 β€” command canceled
  • 4 β€” authentication required πŸ”
NOTE: specific commands may have additional exit codes. Check that command's help for more info. iykyk πŸ’…

🌈 EXAMPLE 🌈

Real examples, straight up:

$ gh project create --owner monalisa --title "Roadmap"
$ gh project view 1 --owner cli --web
$ gh project field-list 1 --owner cli
$ gh project item-list 1 --owner cli

Look at those. Beautiful. Main character commands. ⭐


πŸ’œ SEE ALSO πŸ’œ

  • gh(1) β€” the parent, the blueprint, the blueprint-haver

Okay bestie that's the whole page πŸŽ€ β€” this was GitHub CLI v2.102.0, dated Oct 2026, and you understood all of it, periodt. πŸ’…πŸ”₯

πŸ“¦ where this page comes from