ght not match what is seen on %[1]sgithub.com%[1]s, and new features like regex search are not yet available via the GitHub API. For more information on handling search queries containing a hyphen, run %[1]sgh search --help%[1]s. $ 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" Create a %[1]sworkflow_dispatch%[1]s event for a given workflow. This command will trigger GitHub Actions to run a given workflow file. The given workflow file must support an %[1]son.workflow_dispatch%[1]s trigger in order to be run in this way. If the workflow file supports inputs, they can be specified in a few ways: - Interactively - Via %[1]s-f/--raw-field%[1]s or %[1]s-F/--field%[1]s flags - As JSON, via standard input The created workflow run URL will be returned if available. Verify that a given asset file originated from a specific GitHub Release using cryptographically signed attestations. An attestation is a claim made by GitHub regarding a release and its assets. This command checks that the asset you provide matches a valid attestation for the specified release (or the latest release, if no tag is given). It ensures the asset's integrity by validating that the asset's digest matches the subject in the attestation and that the attestation is associated with the release. query IssueList($owner: String!, $repo: String!, $limit: Int, $endCursor: String, $states: [IssueState!] = OPEN, $assignee: String, $author: String, $mention: String) { repository(owner: $owner, name: $repo) { hasIssuesEnabled issues(first: $limit, after: $endCursor, orderBy: {field: CREATED_AT, direction: DESC}, states: $states, filterBy: {assignee: $assignee, createdBy: $author, mentioned: $mention}) { totalCount nodes { ...issue } pageInfo { hasNextPage endCursor } } } } $ gh pr edit 23 --title "I found a bug" --body "Nothing works" $ gh pr edit 23 --add-label "bug,help wanted" --remove-label "core" $ gh pr edit 23 --add-reviewer monalisa,hubot --remove-reviewer myorg/team-name $ gh pr edit 23 --add-reviewer "@copilot" $ gh pr edit 23 --add-assignee "@me" --remove-assignee monalisa,hubot $ gh pr edit 23 --add-assignee "@copilot" $ gh pr edit 23 --add-project "Roadmap" --remove-project v1,v2 $ gh pr edit 23 --milestone "Version 1" $ gh pr edit 23 --remove-milestone This command configures %[1]sgit%[1]s to use GitHub CLI as a credential helper. For more information on git credential helpers please reference: . By default, GitHub CLI will be set as the credential helper for all authenticated hosts. If there is no authenticated hosts the command fails with an error. Alternatively, use the %[1]s--hostname%[1]s flag to specify a single host to be configured. If the host is not authenticated with, the command fails with an error. statusCheckRollup: commits(last: 1) { nodes { commit { statusCheckRollup { contexts(first:100%s) { nodes { __typename ...on StatusContext { context, state, targetUrl, createdAt, description }, ...on CheckRun { name, checkSuite{workflowRun{workflow{name}}}, status, conclusion, startedAt, completedAt, detailsUrl } }, pageInfo{hasNextPage,endCursor} } } } } } gh follows normal conventions regarding exit codes. - If a command completes successfully, the exit code will be 0 - If a command fails for any reason, the exit code will be 1 - If a command is running but gets cancelled, the exit code will be 2 - If a command requires authentication, the exit code will be 4 NOTE: It is possible that a particular command may have more exit codes, so it is a good practice to check documentation for the command if you are relying on exit codes to control some behavior. 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 %[1]s--yes%[1]s flag is ignored and you will be prompted for confirmation. To delete the current repository non-interactively, specify it explicitly (e.g., %[1]sgh repo delete owner/repo --yes%[1]s). Deletion requires authorization with the %[1]sdelete_repo%[1]s scope. To authorize, run %[1]sgh auth refresh -s delete_repo%[1]s Create a fork of a repository. With no argument, creates a fork of the current repository. Otherwise, forks the specified repository. By default, the new fork is set to be your %[1]sorigin%[1]s remote and any existing origin remote is renamed to %[1]supstream%[1]s. To alter this behavior, you can set a name for the new fork's remote with %[1]s--remote-name%[1]s. The %[1]supstream%[1]s remote will be set as the default remote repository. Additional %[1]sgit clone%[1]s flags can be passed after %[1]s--%[1]s. # 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 0in_toto_attestation/v1/resource_descriptor.proto