GH-EXTENSION-EXEC(1)
β¨ NAME β¨
Okay so bestie, welcome to the GH-EXTENSION-EXEC(1) page from the GitHub CLI manual π β this is literally all about gh-extension-exec, aka Execute an installed extension. Periodt.
π SYNOPSIS π
gh extension exec <name> [args] [flags]
πΈ DESCRIPTION πΈ
So you wanna run an extension using its short name? Say less π
. If the extension repo is owner/gh-extension, then you should pass extension. Iconic. You can use this command when the short name conflicts with a core gh command β no cap, that's the whole vibe check π¦.
All arguments after the extension name get forwarded straight to the executable of the extension. The way that forwarding works is honestly giving main character energy β¨.
π 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. iykyk π
π§ EXAMPLE π§
# Execute a label extension instead of the core gh label command
$ gh extension exec label
π SEE ALSO π
gh-extension(1)π«Ά
That's the whole page, bestie β slay π β¨ This gorgeous lil manual page is from GitHub CLI v2.102.0, dated Oct 2026. Mwah π see ya! ππ¦
π¦ 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