Gh-Cli - Repositories

Gh-Cli - Repositories

Pages: 72

gh repo autolink

URL: https://cli.github.com/manual/gh_repo_autolink

Contents:

• gh repo autolink
  • Available commands
  • Options
  • See also

Autolinks link issues, pull requests, commit messages, and release descriptions to external third-party services.

Autolinks require admin role to view or manage.

For more information, see https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources

gh repo gitignore list

URL: https://cli.github.com/manual/gh_repo_gitignore_list

Contents:

• gh repo gitignore list
  • ALIASES
  • See also

List available repository gitignore templates

Examples:

Example 1 (unknown):

gh repo gitignore list

gh label list

URL: https://cli.github.com/manual/gh_label_list

Contents:

• gh label list
  • Options
  • Options inherited from parent commands
  • ALIASES
  • JSON Fields
  • Examples
  • See also

Display labels in a GitHub repository.

When using the --search flag results are sorted by best match of the query. This behavior cannot be configured with the --order or --sort flags.

color, createdAt, description, id, isDefault, name, updatedAt, url

Examples:

Example 1 (unknown):

gh label list [flags]

Example 2 (bash):

# Sort labels by name
$ gh label list --sort name

# Find labels with "bug" in the name or description
$ gh label list --search bug

gh repo rename

URL: https://cli.github.com/manual/gh_repo_rename

Contents:

• gh repo rename
  • Options
  • Examples
  • See also

Rename a GitHub repository.

is the desired repository name without the owner.

By default, the current repository is renamed. Otherwise, the repository specified with --repo is renamed.

To transfer repository ownership to another user account or organization, you must follow additional steps on github.com.

For more information on transferring repository ownership, see: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository

Examples:

Example 1 (unknown):

gh repo rename [<new-name>] [flags]

Example 2 (bash):

# Rename the current repository (foo/bar -> foo/baz)
$ gh repo rename baz

# Rename the specified repository (qux/quux -> qux/baz)
$ gh repo rename -R qux/quux baz

gh repo clone

URL: https://cli.github.com/manual/gh_repo_clone

Contents:

• gh repo clone
  • Options
  • Examples
  • See also
  • In use
    • Using OWNER/REPO syntax
    • Using other selectors

Clone a GitHub repository locally. Pass additional git clone flags by listing them after --.

If the OWNER/ portion of the OWNER/REPO repository argument is omitted, it defaults to the name of the authenticating user.

When a protocol scheme is not provided in the repository argument, the git_protocol will be chosen from your configuration, which can be checked via gh config get git_protocol. If the protocol scheme is provided, the repository will be cloned using the specified protocol.

If the repository is a fork, its parent repository will be added as an additional git remote called upstream. The remote name can be configured using --upstream-remote-name. The --upstream-remote-name option supports an @owner value which will name the remote after the owner of the parent repository.

If the repository is a fork, its parent repository will be set as the default remote repository.

You can clone any repository using OWNER/REPO syntax.

You can also use GitHub URLs to clone repositories.

Examples:

Example 1 (unknown):

gh repo clone <repository> [<directory>] [-- <gitflags>...]

Example 2 (bash):

# Clone a repository from a specific org
$ gh repo clone cli/cli

# Clone a repository from your own account
$ gh repo clone myrepo

# Clone a repo, overriding git protocol configuration
$ gh repo clone https://github.com/cli/cli
$ gh repo clone git@github.com:cli/cli.git

# Clone a repository to a custom directory
$ gh repo clone cli/cli workspace/cli

# Clone a repository with additional git clone flags
$ gh repo clone cli/cli -- --depth=1

Example 3 (unknown):

# Cloning a repository
~/Projects$ gh repo clone cli/cli
Cloning into 'cli'...
~/Projects$ cd cli
~/Projects/cli$

Example 4 (unknown):

# Cloning a repository
~/Projects/my-project$ gh repo clone https://github.com/cli/cli
Cloning into 'cli'...
remote: Enumerating objects: 99, done.
remote: Counting objects: 100% (99/99), done.
remote: Compressing objects: 100% (76/76), done.
remote: Total 21160 (delta 49), reused 35 (delta 18), pack-reused 21061
Receiving objects: 100% (21160/21160), 57.93 MiB | 10.82 MiB/s, done.
Resolving deltas: 100% (16051/16051), done.

~/Projects/my-project$

gh repo autolink list

URL: https://cli.github.com/manual/gh_repo_autolink_list

Contents:

• gh repo autolink list
  • Options
  • Options inherited from parent commands
  • ALIASES
  • JSON Fields
  • See also

Gets all autolink references that are configured for a repository.

Information about autolinks is only available to repository administrators.

id, isAlphanumeric, keyPrefix, urlTemplate

Examples:

Example 1 (unknown):

gh repo autolink list [flags]

gh pr status

URL: https://cli.github.com/manual/gh_pr_status

Contents:

• gh pr status
  • Options
  • Options inherited from parent commands
  • JSON Fields
  • See also
  • In use

Show status of relevant pull requests.

The status shows a summary of pull requests that includes information such as pull request number, title, CI checks, reviews, etc.

To see more details of CI checks, run gh pr checks.

additions, assignees, author, autoMergeRequest, baseRefName, baseRefOid, body, changedFiles, closed, closedAt, closingIssuesReferences, comments, commits, createdAt, deletions, files, fullDatabaseId, headRefName, headRefOid, headRepository, headRepositoryOwner, id, isCrossRepository, isDraft, labels, latestReviews, maintainerCanModify, mergeCommit, mergeStateStatus, mergeable, mergedAt, mergedBy, milestone, number, potentialMergeCommit, projectCards, projectItems, reactionGroups, reviewDecision, reviewRequests, reviews, state, statusCheckRollup, title, updatedAt, url

Examples:

Example 1 (unknown):

gh pr status [flags]

Example 2 (unknown):

# Viewing the status of your relevant pull requests
~/Projects/my-project$ gh pr status
Current branch
  #12 Remove the test feature [user:patch-2]
   - All checks failing - Review required

Created by you
  You have no open pull requests

Requesting a code review from you
  #13 Fix tests [branch]
  - 3/4 checks failing - Review required
  #15 New feature [branch]
   - Checks passing - Approved

~/Projects/my-project$

gh agent-task create

URL: https://cli.github.com/manual/gh_agent-task_create

Contents:

• gh agent-task create
  • Options
  • Examples
  • See also

Create an agent task (preview)

Examples:

Example 1 (unknown):

gh agent-task create [<task description>] [flags]

Example 2 (bash):

# Create a task from an inline description
$ gh agent-task create "build me a new app"

# Create a task from an inline description and follow logs
$ gh agent-task create "build me a new app" --follow

# Create a task from a file
$ gh agent-task create -F task-desc.md

# Create a task with problem statement from stdin
$ echo "build me a new app" | gh agent-task create -F -

# Create a task with an editor
$ gh agent-task create

# Create a task with an editor and a file as a template
$ gh agent-task create -F task-desc.md

# Select a different base branch for the PR
$ gh agent-task create "fix errors" --base branch

gh project unlink

URL: https://cli.github.com/manual/gh_project_unlink

Contents:

• gh project unlink
  • Options
  • Examples
  • See also

Unlink a project from a repository or a team

Examples:

Example 1 (unknown):

gh project unlink [<number>] [flags]

Example 2 (bash):

# Unlink monalisa's project 1 from her repository "my_repo"
$ gh project unlink 1 --owner monalisa --repo my_repo

# Unlink monalisa's organization's project 1 from her team "my_team"
$ gh project unlink 1 --owner my_organization --team my_team

# Unlink monalisa's project 1 from the repository of current directory if neither --repo nor --team is specified
$ gh project unlink 1

gh repo

URL: https://cli.github.com/manual/gh_repo

Contents:

• gh repo
  • General commands
  • Targeted commands
  • Examples
  • See also

Work with GitHub repositories.

Examples:

Example 1 (bash):

$ gh repo create
$ gh repo clone cli/cli
$ gh repo view --web

gh project link

URL: https://cli.github.com/manual/gh_project_link

Contents:

• gh project link
  • Options
  • Examples
  • See also

Link a project to a repository or a team

Examples:

Example 1 (unknown):

gh project link [<number>] [flags]

Example 2 (bash):

# Link monalisa's project 1 to her repository "my_repo"
$ gh project link 1 --owner monalisa --repo my_repo

# Link monalisa's organization's project 1 to her team "my_team"
$ gh project link 1 --owner my_organization --team my_team

# Link monalisa's project 1 to the repository of current directory if neither --repo nor --team is specified
$ gh project link 1

gh repo autolink view

URL: https://cli.github.com/manual/gh_repo_autolink_view

Contents:

• gh repo autolink view
  • Options
  • Options inherited from parent commands
  • JSON Fields
  • See also

View an autolink reference for a repository.

id, isAlphanumeric, keyPrefix, urlTemplate

Examples:

Example 1 (unknown):

gh repo autolink view <id> [flags]

gh label clone

URL: https://cli.github.com/manual/gh_label_clone

Contents:

• gh label clone
  • Options
  • Options inherited from parent commands
  • Examples
  • See also

Clones labels from a source repository to a destination repository on GitHub. By default, the destination repository is the current repository.

All labels from the source repository will be copied to the destination repository. Labels in the destination repository that are not in the source repository will not be deleted or modified.

Labels from the source repository that already exist in the destination repository will be skipped. You can overwrite existing labels in the destination repository using the --force flag.

Examples:

Example 1 (unknown):

gh label clone <source-repository> [flags]

Example 2 (bash):

# Clone and overwrite labels from cli/cli repository into the current repository
$ gh label clone cli/cli --force

# Clone labels from cli/cli repository into a octocat/cli repository
$ gh label clone cli/cli --repo octocat/cli

gh repo list

URL: https://cli.github.com/manual/gh_repo_list

Contents:

• gh repo list
  • Options
  • ALIASES
  • JSON Fields
  • See also

List repositories owned by a user or organization.

Note that the list will only include repositories owned by the provided argument, and the --fork or --source flags will not traverse ownership boundaries. For example, when listing the forks in an organization, the output would not include those owned by individual users.

archivedAt, assignableUsers, codeOfConduct, contactLinks, createdAt, defaultBranchRef, deleteBranchOnMerge, description, diskUsage, forkCount, fundingLinks, hasDiscussionsEnabled, hasIssuesEnabled, hasProjectsEnabled, hasWikiEnabled, homepageUrl, id, isArchived, isBlankIssuesEnabled, isEmpty, isFork, isInOrganization, isMirror, isPrivate, isSecurityPolicyEnabled, isTemplate, isUserConfigurationRepository, issueTemplates, issues, labels, languages, latestRelease, licenseInfo, mentionableUsers, mergeCommitAllowed, milestones, mirrorUrl, name, nameWithOwner, openGraphImageUrl, owner, parent, primaryLanguage, projects, projectsV2, pullRequestTemplates, pullRequests, pushedAt, rebaseMergeAllowed, repositoryTopics, securityPolicyUrl, squashMergeAllowed, sshUrl, stargazerCount, templateRepository, updatedAt, url, usesCustomOpenGraphImage, viewerCanAdminister, viewerDefaultCommitEmail, viewerDefaultMergeMethod, viewerHasStarred, viewerPermission, viewerPossibleCommitEmails, viewerSubscription, visibility, watchers

Examples:

Example 1 (unknown):

gh repo list [<owner>] [flags]

gh issue unpin

URL: https://cli.github.com/manual/gh_issue_unpin

Contents:

• gh issue unpin
  • Options inherited from parent commands
  • Examples
  • See also

Unpin an issue from a repository.

The issue can be specified by issue number or URL.

Examples:

Example 1 (unknown):

gh issue unpin {<number> | <url>}

Example 2 (bash):

# Unpin issue from the current repository
$ gh issue unpin 23

# Unpin issue by URL
$ gh issue unpin https://github.com/owner/repo/issues/23

# Unpin an issue from specific repository
$ gh issue unpin 23 --repo owner/repo

gh repo view

URL: https://cli.github.com/manual/gh_repo_view

Contents:

• gh repo view
  • Options
  • JSON Fields
  • See also
  • In use
    • In terminal
    • In the browser
    • With no arguments

Display the description and the README of a GitHub repository.

With no argument, the repository for the current directory is displayed.

With --web, open the repository in a web browser instead.

With --branch, view a specific branch of the repository.

archivedAt, assignableUsers, codeOfConduct, contactLinks, createdAt, defaultBranchRef, deleteBranchOnMerge, description, diskUsage, forkCount, fundingLinks, hasDiscussionsEnabled, hasIssuesEnabled, hasProjectsEnabled, hasWikiEnabled, homepageUrl, id, isArchived, isBlankIssuesEnabled, isEmpty, isFork, isInOrganization, isMirror, isPrivate, isSecurityPolicyEnabled, isTemplate, isUserConfigurationRepository, issueTemplates, issues, labels, languages, latestRelease, licenseInfo, mentionableUsers, mergeCommitAllowed, milestones, mirrorUrl, name, nameWithOwner, openGraphImageUrl, owner, parent, primaryLanguage, projects, projectsV2, pullRequestTemplates, pullRequests, pushedAt, rebaseMergeAllowed, repositoryTopics, securityPolicyUrl, squashMergeAllowed, sshUrl, stargazerCount, templateRepository, updatedAt, url, usesCustomOpenGraphImage, viewerCanAdminister, viewerDefaultCommitEmail, viewerDefaultMergeMethod, viewerHasStarred, viewerPermission, viewerPossibleCommitEmails, viewerSubscription, visibility, watchers

By default, we will display items in the terminal.

Quickly open an item in the browser using --web or -w

We will display the repository you're currently in.

Examples:

Example 1 (unknown):

gh repo view [<repository>] [flags]

Example 2 (unknown):

# Viewing a repository in terminal
~/Projects/my-project$ gh repo view owner/repo
owner/repo
Repository description

  Repository README

View this repository on GitHub: https://github.com/owner/repo/
~/Projects/my-project$

Example 3 (unknown):

# Viewing a repository in the browser
~/Projects$ gh repo view owner/repo --web
Opening https://github.com/owner/repo/ in your browser.
~/Projects$

Example 4 (unknown):

# Viewing the repository you're in
~/Projects/my-project$ gh repo view
owner/my-project
Repository description

  Repository README

View this repository on GitHub: https://github.com/owner/repo/
~/Projects/my-project$

gh gist clone

URL: https://cli.github.com/manual/gh_gist_clone

Contents:

• gh gist clone
  • See also

Clone a GitHub gist locally.

A gist can be supplied as argument in either of the following formats:

Pass additional git clone flags by listing them after --.

Examples:

Example 1 (unknown):

gh gist clone <gist> [<directory>] [-- <gitflags>...]

gh codespace create

URL: https://cli.github.com/manual/gh_codespace_create

Contents:

• gh codespace create
  • Options
  • See also

Examples:

Example 1 (unknown):

gh codespace create [flags]

gh repo delete

URL: https://cli.github.com/manual/gh_repo_delete

Contents:

• gh repo delete
  • Options
  • See also

Delete a GitHub repository.

With no argument, deletes the current repository. Otherwise, deletes the specified repository.

For safety, when no repository argument is provided, the --yes flag is ignored and you will be prompted for confirmation. To delete the current repository non-interactively, specify it explicitly (e.g., gh repo delete owner/repo --yes).

Deletion requires authorization with the delete_repo scope. To authorize, run gh auth refresh -s delete_repo

Examples:

Example 1 (unknown):

gh repo delete [<repository>] [flags]

gh repo deploy-key add

URL: https://cli.github.com/manual/gh_repo_deploy-key_add

Contents:

• gh repo deploy-key add
  • Options
  • Options inherited from parent commands
  • Examples
  • See also

Add a deploy key to a GitHub repository.

Note that any key added by gh will be associated with the current authentication token. If you de-authorize the GitHub CLI app or authentication token from your account, any deploy keys added by GitHub CLI will be removed as well.

Examples:

Example 1 (unknown):

gh repo deploy-key add <key-file> [flags]

Example 2 (bash):

# Generate a passwordless SSH key and add it as a deploy key to a repository
$ ssh-keygen -t ed25519 -C "my description" -N "" -f ~/.ssh/gh-test
$ gh repo deploy-key add ~/.ssh/gh-test.pub

gh repo gitignore view

URL: https://cli.github.com/manual/gh_repo_gitignore_view

Contents:

• gh repo gitignore view
  • Examples
  • See also

View an available repository .gitignore template.

is a case-sensitive .gitignore template name.

For a list of available templates, run gh repo gitignore list.

Examples:

Example 1 (unknown):

gh repo gitignore view <template>

Example 2 (bash):

# View the Go gitignore template
$ gh repo gitignore view Go

# View the Python gitignore template
$ gh repo gitignore view Python

# Create a new .gitignore file using the Go template
$ gh repo gitignore view Go > .gitignore

# Create a new .gitignore file using the Python template
$ gh repo gitignore view Python > .gitignore

gh issue edit

URL: https://cli.github.com/manual/gh_issue_edit

Contents:

• gh issue edit
  • Options
  • Options inherited from parent commands
  • Examples
  • See also

Edit one or more issues within the same repository.

Editing issues' projects requires authorization with the project scope. To authorize, run gh auth refresh -s project.

The --add-assignee and --remove-assignee flags both support the following special values:

Examples:

Example 1 (unknown):

gh issue edit {<numbers> | <urls>} [flags]

Example 2 (bash):

$ gh issue edit 23 --title "I found a bug" --body "Nothing works"
$ gh issue edit 23 --add-label "bug,help wanted" --remove-label "core"
$ gh issue edit 23 --add-assignee "@me" --remove-assignee monalisa,hubot
$ gh issue edit 23 --add-assignee "@copilot"
$ gh issue edit 23 --add-project "Roadmap" --remove-project v1,v2
$ gh issue edit 23 --milestone "Version 1"
$ gh issue edit 23 --remove-milestone
$ gh issue edit 23 --body-file body.txt
$ gh issue edit 23 34 --add-label "help wanted"

gh release list

URL: https://cli.github.com/manual/gh_release_list

Contents:

• gh release list
  • Options
  • Options inherited from parent commands
  • ALIASES
  • JSON Fields
  • See also

List releases in a repository

createdAt, isDraft, isLatest, isPrerelease, name, publishedAt, tagName

Examples:

Example 1 (unknown):

gh release list [flags]

gh variable list

URL: https://cli.github.com/manual/gh_variable_list

Contents:

• gh variable list
  • Options
  • Options inherited from parent commands
  • ALIASES
  • JSON Fields
  • See also

List variables on one of the following levels:

createdAt, name, numSelectedRepos, selectedReposURL, updatedAt, value, visibility

Examples:

Example 1 (unknown):

gh variable list [flags]

gh project item-create

URL: https://cli.github.com/manual/gh_project_item-create

Contents:

• gh project item-create
  • Options
  • Examples
  • See also

Create a draft issue item in a project

Examples:

Example 1 (unknown):

gh project item-create [<number>] [flags]

Example 2 (bash):

# Create a draft issue in the current user's project "1"
$ gh project item-create 1 --owner "@me" --title "new item" --body "new item body"

gh repo deploy-key

URL: https://cli.github.com/manual/gh_repo_deploy-key

Contents:

• gh repo deploy-key
  • Available commands
  • Options
  • See also

Manage deploy keys in a repository

gh repo sync

URL: https://cli.github.com/manual/gh_repo_sync

Contents:

• gh repo sync
  • Options
  • Examples
  • See also

Sync destination repository from source repository. Syncing uses the default branch of the source repository to update the matching branch on the destination repository so they are equal. A fast forward update will be used except when the --force flag is specified, then the two branches will be synced using a hard reset.

Without an argument, the local repository is selected as the destination repository.

The source repository is the parent of the destination repository by default. This can be overridden with the --source flag.

Examples:

Example 1 (unknown):

gh repo sync [<destination-repository>] [flags]

Example 2 (bash):

# Sync local repository from remote parent
$ gh repo sync

# Sync local repository from remote parent on specific branch
$ gh repo sync --branch v1

# Sync remote fork from its parent
$ gh repo sync owner/cli-fork

# Sync remote repository from another remote repository
$ gh repo sync owner/repo --source owner2/repo2

gh codespace list

URL: https://cli.github.com/manual/gh_codespace_list

Contents:

• gh codespace list
  • Options
  • ALIASES
  • JSON Fields
  • See also

List codespaces of the authenticated user.

Alternatively, organization administrators may list all codespaces billed to the organization.

gh cs ls, gh codespace ls

createdAt, displayName, gitStatus, lastUsedAt, machineName, name, owner, repository, state, vscsTarget

Examples:

Example 1 (unknown):

gh codespace list [flags]

gh variable

URL: https://cli.github.com/manual/gh_variable

Contents:

• gh variable
  • Available commands
  • Options
  • See also

Variables can be set at the repository, environment or organization level for use in GitHub Actions or Dependabot. Run gh help variable set to learn how to get started.

gh pr checkout

URL: https://cli.github.com/manual/gh_pr_checkout

Contents:

• gh pr checkout
  • Options
  • Options inherited from parent commands
  • ALIASES
  • Examples
  • See also
  • In use
    • Using pull request number
    • Using other selectors

Check out a pull request in git

You can check out any pull request, including from forks, in a repository using its pull request number

You can also use URLs and branch names to checkout pull requests.

Examples:

Example 1 (unknown):

gh pr checkout [<number> | <url> | <branch>] [flags]

Example 2 (bash):

# Interactively select a PR from the 10 most recent to check out
$ gh pr checkout

# Checkout a specific PR
$ gh pr checkout 32
$ gh pr checkout https://github.com/OWNER/REPO/pull/32
$ gh pr checkout feature

Example 3 (unknown):

// Checking out a pull request locally
~/Projects/my-project$ gh pr checkout 12
remote: Enumerating objects: 66, done.
remote: Counting objects: 100% (66/66), done.
remote: Total 83 (delta 66), reused 66 (delta 66), pack-reused 17
Unpacking objects: 100% (83/83), done.
From https://github.com/owner/repo
 * [new ref]             refs/pull/8896/head -> patch-2
M       README.md
Switched to branch 'patch-2'

~/Projects/my-project$

Example 4 (unknown):

// Checking out a pull request locally
~/Projects/my-project$ gh pr checkout branch-name
Switched to branch 'branch-name'
Your branch is up to date with 'origin/branch-name'.
Already up to date.

~/Projects/my-project$

gh repo archive

URL: https://cli.github.com/manual/gh_repo_archive

Contents:

• gh repo archive
  • Options
  • See also

Archive a GitHub repository.

With no argument, archives the current repository.

Examples:

Example 1 (unknown):

gh repo archive [<repository>] [flags]

gh release create

URL: https://cli.github.com/manual/gh_release_create

Contents:

• gh release create
  • Options
  • Options inherited from parent commands
  • ALIASES
  • Examples
  • See also

Create a new GitHub Release for a repository.

A list of asset files may be given to upload to the new release. To define a display label for an asset, append text starting with # after the file name.

If a matching git tag does not yet exist, one will automatically get created from the latest state of the default branch. Use --target to point to a different branch or commit for the automatic tag creation. Use --verify-tag to abort the release if the tag doesn't already exist. To fetch the new tag locally after the release, do git fetch --tags origin.

To create a release from an annotated git tag, first create one locally with git, push the tag to GitHub, then run this command. Use --notes-from-tag to get the release notes from the annotated git tag. If the tag is not annotated, the commit message will be used instead.

Use --generate-notes to automatically generate notes using GitHub Release Notes API. When using automatically generated release notes, a release title will also be automatically generated unless a title was explicitly passed. Additional release notes can be prepended to automatically generated notes by using the --notes flag.

By default, the release is created even if there are no new commits since the last release. This may result in the same or duplicate release which may not be desirable in some cases. Use --fail-on-no-commits to fail if no new commits are available. This flag has no effect if there are no existing releases or this is the very first release.

Examples:

Example 1 (unknown):

gh release create [<tag>] [<filename>... | <pattern>...]

Example 2 (bash):

# Interactively create a release
$ gh release create

# Interactively create a release from specific tag
$ gh release create v1.2.3

# Non-interactively create a release
$ gh release create v1.2.3 --notes "bugfix release"

# Use automatically generated via GitHub Release Notes API release notes
$ gh release create v1.2.3 --generate-notes

# Use release notes from a file
$ gh release create v1.2.3 -F release-notes.md

# Use tag annotation or associated commit message as notes
$ gh release create v1.2.3 --notes-from-tag

# Don't mark the release as latest
$ gh release create v1.2.3 --latest=false

# Upload all tarballs in a directory as release assets
$ gh release create v1.2.3 ./dist/*.tgz

# Upload a release asset with a display label
$ gh release create v1.2.3 '/path/to/asset.zip#My display label'

# Create a release and start a discussion
$ gh release create v1.2.3 --discussion-category "General"

# Create a release only if there are new commits available since the last release
$ gh release create v1.2.3 --fail-on-no-commits

gh issue pin

URL: https://cli.github.com/manual/gh_issue_pin

Contents:

• gh issue pin
  • Options inherited from parent commands
  • Examples
  • See also

Pin an issue to a repository.

The issue can be specified by issue number or URL.

Examples:

Example 1 (unknown):

gh issue pin {<number> | <url>}

Example 2 (bash):

# Pin an issue to the current repository
$ gh issue pin 23

# Pin an issue by URL
$ gh issue pin https://github.com/owner/repo/issues/23

# Pin an issue to specific repository
$ gh issue pin 23 --repo owner/repo

gh repo deploy-key delete

URL: https://cli.github.com/manual/gh_repo_deploy-key_delete

Contents:

• gh repo deploy-key delete
  • Options inherited from parent commands
  • See also

Delete a deploy key from a GitHub repository

Examples:

Example 1 (unknown):

gh repo deploy-key delete <key-id>

gh extension

URL: https://cli.github.com/manual/gh_extension

Contents:

• gh extension
  • Available commands
  • ALIASES
  • See also

GitHub CLI extensions are repositories that provide additional gh commands.

The name of the extension repository must start with gh- and it must contain an executable of the same name. All arguments passed to the gh invocation will be forwarded to the gh- executable of the extension.

An extension cannot override any of the core gh commands. If an extension name conflicts with a core gh command, you can use gh extension exec .

When an extension is executed, gh will check for new versions once every 24 hours and display an upgrade notice. See gh help environment for information on disabling extension notices.

For the list of available extensions, see https://github.com/topics/gh-extension.

gh ext, gh extensions

gh ruleset check

URL: https://cli.github.com/manual/gh_ruleset_check

Contents:

• gh ruleset check
  • Options
  • Options inherited from parent commands
  • Examples
  • See also

View information about GitHub rules that apply to a given branch.

The provided branch name does not need to exist; rules will be displayed that would apply to a branch with that name. All rules are returned regardless of where they are configured.

If no branch name is provided, then the current branch will be used.

The --default flag can be used to view rules that apply to the default branch of the repository.

Examples:

Example 1 (unknown):

gh ruleset check [<branch>] [flags]

Example 2 (bash):

# View all rules that apply to the current branch
$ gh ruleset check

# View all rules that apply to a branch named "my-branch" in a different repository
$ gh ruleset check my-branch --repo owner/repo

# View all rules that apply to the default branch in a different repository
$ gh ruleset check --default --repo owner/repo

# View a ruleset configured in a different repository or any of its parents
$ gh ruleset view 23 --repo owner/repo

# View an organization-level ruleset
$ gh ruleset view 23 --org my-org

gh codespace delete

URL: https://cli.github.com/manual/gh_codespace_delete

Contents:

• gh codespace delete
  • Options
  • See also

Delete codespaces based on selection criteria.

All codespaces for the authenticated user can be deleted, as well as codespaces for a specific repository. Alternatively, only codespaces older than N days can be deleted.

Organization administrators may delete any codespace billed to the organization.

Examples:

Example 1 (unknown):

gh codespace delete [flags]

gh pr list

URL: https://cli.github.com/manual/gh_pr_list

Contents:

• gh pr list
  • Options
  • Options inherited from parent commands
  • ALIASES
  • JSON Fields
  • Examples
  • See also
  • In use
    • Default behavior
    • Filtering with flags

List pull requests in a GitHub repository. By default, this only lists open PRs.

The search query syntax is documented here: https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests

On supported GitHub hosts, advanced issue search syntax can be used in the --search query. For more information about advanced issue search, see: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests#building-advanced-filters-for-issues

additions, assignees, author, autoMergeRequest, baseRefName, baseRefOid, body, changedFiles, closed, closedAt, closingIssuesReferences, comments, commits, createdAt, deletions, files, fullDatabaseId, headRefName, headRefOid, headRepository, headRepositoryOwner, id, isCrossRepository, isDraft, labels, latestReviews, maintainerCanModify, mergeCommit, mergeStateStatus, mergeable, mergedAt, mergedBy, milestone, number, potentialMergeCommit, projectCards, projectItems, reactionGroups, reviewDecision, reviewRequests, reviews, state, statusCheckRollup, title, updatedAt, url

You will see the most recent 30 open items.

You can use flags to filter the list for your specific use cases.

Examples:

Example 1 (unknown):

gh pr list [flags]

Example 2 (bash):

# List PRs authored by you
$ gh pr list --author "@me"

# List PRs with a specific head branch name
$ gh pr list --head "typo"

# List only PRs with all of the given labels
$ gh pr list --label bug --label "priority 1"

# Filter PRs using search syntax
$ gh pr list --search "status:success review:required"

# Find a PR that introduced a given commit
$ gh pr list --search "<SHA>" --state merged

Example 3 (unknown):

# Viewing a list of open pull requests
~/Projects/my-project$ gh pr list

Pull requests for owner/repo

#14  Upgrade to Prettier 1.19                           prettier
#14  Extend arrow navigation in lists for MacOS         arrow-nav
#13  Add Support for Windows Automatic Dark Mode        dark-mode
#8   Create and use keyboard shortcut react component   shortcut

~/Projects/my-project$

Example 4 (unknown):

# Viewing a list of closed pull requests assigned to a user
~/Projects/my-project$ gh pr list --state closed --assignee user

Pull requests for owner/repo

#13  Upgrade to Electron 7         electron-7
#8   Release Notes Writing Guide   release-notes

~/Projects/my-project$

gh issue transfer

URL: https://cli.github.com/manual/gh_issue_transfer

Contents:

• gh issue transfer
  • Options inherited from parent commands
  • See also

Transfer issue to another repository

Examples:

Example 1 (unknown):

gh issue transfer {<number> | <url>} <destination-repo>

gh extension exec

URL: https://cli.github.com/manual/gh_extension_exec

Contents:

• gh extension exec
  • Examples
  • See also

Execute an extension using the short name. For example, if the extension repository is owner/gh-extension, you should pass extension. You can use this command when the short name conflicts with a core gh command.

All arguments after the extension name will be forwarded to the executable of the extension.

Examples:

Example 1 (unknown):

gh extension exec <name> [args]

Example 2 (bash):

# Execute a label extension instead of the core gh label command
$ gh extension exec label

gh extension create

URL: https://cli.github.com/manual/gh_extension_create

Contents:

• gh extension create
  • Options
  • Examples
  • See also

Create a new extension

Examples:

Example 1 (unknown):

gh extension create [<name>] [flags]

Example 2 (bash):

# Use interactively
$ gh extension create

# Create a script-based extension
$ gh extension create foobar

# Create a Go extension
$ gh extension create --precompiled=go foobar

# Create a non-Go precompiled extension
$ gh extension create --precompiled=other foobar

gh repo create

URL: https://cli.github.com/manual/gh_repo_create

Contents:

• gh repo create
  • Options
  • ALIASES
  • Examples
  • See also

Create a new GitHub repository.

To create a repository interactively, use gh repo create with no arguments.

To create a remote repository non-interactively, supply the repository name and one of --public, --private, or --internal. Pass --clone to clone the new repository locally.

If the OWNER/ portion of the OWNER/REPO name argument is omitted, it defaults to the name of the authenticating user.

To create a remote repository from an existing local repository, specify the source directory with --source. By default, the remote repository name will be the name of the source directory.

Pass --push to push any local commits to the new repository. If the repo is bare, this will mirror all refs.

For language or platform .gitignore templates to use with --gitignore, https://github.com/github/gitignore.

For license keywords to use with --license, run gh repo license list or visit https://choosealicense.com.

The repo is created with the configured repository default branch, see https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.

Examples:

Example 1 (unknown):

gh repo create [<name>] [flags]

Example 2 (bash):

# Create a repository interactively
$ gh repo create

# Create a new remote repository and clone it locally
$ gh repo create my-project --public --clone

# Create a new remote repository in a different organization
$ gh repo create my-org/my-project --public

# Create a remote repository from the current directory
$ gh repo create my-project --private --source=. --remote=upstream

gh issue list

URL: https://cli.github.com/manual/gh_issue_list

Contents:

• gh issue list
  • Options
  • Options inherited from parent commands
  • ALIASES
  • JSON Fields
  • Examples
  • See also
  • In use
    • Default behavior
    • Filtering with flags

List issues in a GitHub repository. By default, this only lists open issues.

The search query syntax is documented here: https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests

On supported GitHub hosts, advanced issue search syntax can be used in the --search query. For more information about advanced issue search, see: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests#building-advanced-filters-for-issues

assignees, author, body, closed, closedAt, closedByPullRequestsReferences, comments, createdAt, id, isPinned, labels, milestone, number, projectCards, projectItems, reactionGroups, state, stateReason, title, updatedAt, url

You will see the most recent 30 open items.

You can use flags to filter the list for your specific use cases.

Examples:

Example 1 (unknown):

gh issue list [flags]

Example 2 (bash):

$ gh issue list --label "bug" --label "help wanted"
$ gh issue list --author monalisa
$ gh issue list --assignee "@me"
$ gh issue list --milestone "The big 1.0"
$ gh issue list --search "error no:assignee sort:created-asc"
$ gh issue list --state all

Example 3 (unknown):

# Viewing a list of open issues
~/Projects/my-project$ gh issue list

Issues for owner/repo

#14  Update the remote url if it changed  (bug)
#14  PR commands on a detached head       (enhancement)
#13  Support for GitHub Enterprise        (wontfix)
#8   Add an easier upgrade command        (bug)

~/Projects/my-project$

Example 4 (unknown):

# Viewing a list of closed issues assigned to a user
~/Projects/my-project$ gh issue list --state closed --assignee user

Issues for owner/repo

#13  Enable discarding submodule changes  (bug)
#8   Upgrade to latest react              (upgrade)

~/Projects/my-project$

gh repo deploy-key list

URL: https://cli.github.com/manual/gh_repo_deploy-key_list

Contents:

• gh repo deploy-key list
  • Options
  • Options inherited from parent commands
  • ALIASES
  • JS

…(truncated)