All checks were successful
Test / frontend-tests (pull_request) Successful in 1m9s
Test / frontend-typecheck (pull_request) Successful in 1m15s
Test / rust-fmt-check (pull_request) Successful in 2m44s
Test / rust-clippy (pull_request) Successful in 24m22s
Test / rust-tests (pull_request) Successful in 25m43s
- Fix TypeScript lint errors in setup.ts and LogUpload - Remove unused imports and variables - Fix duplicate Separator exports in ui/index.tsx - Apply cargo fmt formatting to Rust code - Update ESLint configuration
48 lines
922 B
Groff
48 lines
922 B
Groff
.nh
|
|
.TH "GH-EXTENSION-EXEC" "1" "Nov 2024" "GitHub CLI 2.63.0" "GitHub CLI manual"
|
|
|
|
.SH NAME
|
|
gh-extension-exec - Execute an installed extension
|
|
|
|
|
|
.SH SYNOPSIS
|
|
\fBgh extension exec <name> [args] [flags]\fR
|
|
|
|
|
|
.SH DESCRIPTION
|
|
Execute an extension using the short name. For example, if the extension repository is
|
|
\fBowner/gh-extension\fR, you should pass \fBextension\fR\&. You can use this command when
|
|
the short name conflicts with a core gh command.
|
|
|
|
.PP
|
|
All arguments after the extension name will be forwarded to the executable
|
|
of the extension.
|
|
|
|
|
|
.SH EXIT CODES
|
|
0: Successful execution
|
|
|
|
.PP
|
|
1: Error
|
|
|
|
.PP
|
|
2: Command canceled
|
|
|
|
.PP
|
|
4: Authentication required
|
|
|
|
.PP
|
|
NOTE: Specific commands may have additional exit codes. Refer to the command's help for more information.
|
|
|
|
|
|
.SH EXAMPLE
|
|
.EX
|
|
# execute a label extension instead of the core gh label command
|
|
$ gh extension exec label
|
|
|
|
.EE
|
|
|
|
|
|
.SH SEE ALSO
|
|
\fBgh-extension(1)\fR
|