GH-EXTENSION-SEARCH(1)

πŸ’… GH-EXTENSION-SEARCH(1) β€” like, the official GitHub CLI manual, bestie πŸŽ€

okay so this is a page from the GitHub CLI manual β€” yes, that GitHub CLI β€” and it's all about finding yourself some extensions. buckle up, it's gonna be cute and also extremely useful ✨


🌸 NAME 🌸

gh-extension-search β€” search extensions to the GitHub CLI. that's it, that's the whole vibe check πŸ¦‹


✨ SYNOPSIS ✨

gh extension search [<query>] [flags]

πŸ’– DESCRIPTION πŸ’–

Search for gh extensions. simple as that, no cap πŸ”₯

With no arguments, this command prints out the first 30 extensions available to install, sorted by number of stars. thirty! that's your starter pack. want more? just specify a higher limit with the --limit flag and go off πŸ‘‘

So when you're connected to a terminal, this command prints out three columns:

  • the first has a βœ“ if the extension is already installed locally (a little checkmark, a little "yes bestie you already have this one" πŸ’…)
  • the second is the full name of the extension repository in OWNER/REPO format
  • the third is the extension's description

When you're not connected to a terminal, the βœ“ character is rendered as the word installed instead β€” but otherwise the order and content of the columns are the same. same energy, more letters 🫢

This command behaves similarly to gh search repos but does not support as many search qualifiers 😭 so for a finer grained search of extensions, try using:

gh search repos --topic "gh-extension"

and adding qualifiers as needed. See gh help search repos to learn more about repository search. iykyk ⭐

And for listing just the extensions that are already installed locally, see:

gh ext list

πŸŽ€ OPTIONS πŸŽ€

  • -q, --jq <expression> β€” filter JSON output using a jq expression. yes, the jq you know and love πŸ’œ
  • --json <fields> β€” output JSON with the specified fields
  • --license <strings> β€” filter based on license type
  • -L, --limit <int> (default 30) β€” maximum number of extensions to fetch. defaults to 30, but the limit does not exist if you don't want it to 🌈
  • --order <string> (default "desc") β€” order of repositories returned, ignored unless the --sort flag is specified: {asc|desc}
  • --owner <strings> β€” filter on owner
  • --sort <string> (default "best-match") β€” sort fetched repositories: {forks|help-wanted-issues|stars|updated}
  • -t, --template <string> β€” format JSON output using a Go template; see gh help formatting
  • -w, --web β€” open the search query in the web browser 🌐

🌟 JSON FIELDS 🌟

these are the fields you can ask for, all of them, no skips πŸ™ˆ

createdAt, defaultBranch, description, forksCount, fullName, hasDownloads, hasIssues, hasPages, hasProjects, hasWiki, homepage, id, isArchived, isDisabled, isFork, isPrivate, language, license, name, openIssuesCount, owner, pushedAt, size, stargazersCount, updatedAt, url, visibility, watchersCount


🧚 EXIT CODES 🧚

  • 0: successful execution β€” slay πŸŽ‰
  • 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. fr fr, always check πŸ‘€

πŸ“ EXAMPLE πŸ“

# List the first 30 extensions sorted by star count, descending
$ gh ext search

# List more extensions
$ gh ext search --limit 300

# List extensions matching the term "branch"
$ gh ext search branch

# List extensions owned by organization "github"
$ gh ext search --owner github

# List extensions, sorting by recently updated, ascending
$ gh ext search --sort updated --order asc

# List extensions, filtering by license
$ gh ext search --license MIT

# Open search results in the browser
$ gh ext search -w

πŸ¦‹ SEE ALSO πŸ¦‹

  • gh-extension(1) β€” go read it, bestie, it's giving main character energy πŸ‘‘

okay that's the whole page!! brought to you by GitHub CLI v2.102.0, dated Oct 2026 β€” mwah, go install something cute πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from