.nh
.TH "GT-ISSUE-ATTACHMENT-DELETE" "1" "Nov 2026" "gitea-cli" "gitea-cli Manual"

.SH NAME
gt-issue-attachment-delete - Delete an attachment


.SH SYNOPSIS
\fBgt issue attachment delete {<number> | <url>} <attachment-id> [flags]\fP


.SH DESCRIPTION
Delete an attachment

.SS ARGUMENTS
.EX
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.
.EE


.SH OPTIONS
\fB-h\fP, \fB--help\fP[=false]
	help for delete


.SH OPTIONS INHERITED FROM PARENT COMMANDS
\fB--cwd\fP=""
	Working \fBdirectory\fR for repository discovery

.PP
\fB--debug\fP[=false]
	Log the method, URL, status, and duration of each HTTP request to stderr

.PP
\fB--host\fP=""
	Gitea instance \fBURL\fR, including any base path

.PP
\fB--interactive\fP[=false]
	Allow prompts with machine output

.PP
\fB--no-input\fP[=false]
	Disable prompts and implicit editor/browser interactions

.PP
\fB--remote\fP=""
	Git \fBremote\fR used for repository discovery

.PP
\fB-R\fP, \fB--repo\fP=""
	Select a repository as \fBOWNER/REPO\fR or URL

.PP
\fB--sudo\fP=""
	Perform API requests as this \fBuser\fR (requires an administrator account)

.PP
\fB--user\fP=""
	Account \fBname\fR on the selected instance

.PP
\fB-y\fP, \fB--yes\fP[=false]
	Accept confirmations without prompting


.SH EXAMPLE
.EX
$ gt issue attachment delete 12 9 --yes
.EE


.SH SEE ALSO
\fBgt-issue-attachment(1)\fP