| GT-ISSUE-DELETE(1) | gitea-cli Manual | GT-ISSUE-DELETE(1) |
NAME
gt-issue-delete - Delete issues
SYNOPSIS
gt issue delete {<number> | <url>}... [flags]
DESCRIPTION
Delete issues for good, with their comments, attachments and time tracking. This cannot be undone and needs the permission to delete issues, which Gitea gives repository owners and administrators. To only stop work on one, use gt issue close. To delete a pull request, use gt pr delete.
ARGUMENTS
An issue can be supplied as argument in any of the following formats: - by number, e.g. "123" or "#123" - by URL, e.g. "https://gitea.com/OWNER/REPO/issues/123" - by repository and number, e.g. "OWNER/REPO#123" Several issues must be in one repository. Next to "OWNER/REPO#123" or a URL, "124" means OWNER/REPO#124, unless gt targets another repository otherwise, such as the clone's, --repo or GITEA_CLI_REPO: then the command fails, and the number must be qualified.
OPTIONS
--dry-run[=false] Show the write requests gt would send, without sending them
-h, --help[=false] help for delete
OPTIONS INHERITED FROM PARENT COMMANDS
--cwd="" Working directory for repository discovery
--debug[=false] Log the method, URL, status, and duration of each HTTP request to stderr
--host="" Gitea instance URL, including any base path
--interactive[=false] Allow prompts with machine output
--no-input[=false] Disable prompts and implicit editor/browser interactions
--remote="" Git remote used for repository discovery
-R, --repo="" Select a repository as OWNER/REPO or URL
--sudo="" Perform API requests as this user (requires an administrator account)
--user="" Account name on the selected instance
-y, --yes[=false] Accept confirmations without prompting
EXAMPLE
$ gt issue delete 12 $ gt issue delete 12 13 --yes
SEE ALSO
| Nov 2026 | gitea-cli |