GT-ISSUE-UNLOCK(1) gitea-cli Manual GT-ISSUE-UNLOCK(1)

gt-issue-unlock - Unlock the conversation of issues

gt issue unlock {<number> | <url>}... [flags]

Unlock the conversation of issues or pull requests, so that everyone who can see them can comment again.

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.

assignees, author, body, comments, created_at, due_date, id, kind, labels,
milestone, number, ref, state, title, updated_at, url

--dry-run[=false] Show the write requests gt would send, without sending them

-h, --help[=false] help for unlock

--csv[=""] Output CSV with the specified comma-separated fields, or all fields

--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

-q, --jq="" Filter JSON output using a jq expression; implies --json

--json[=""] Output JSON with the specified comma-separated fields, or all fields

--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)

--template="" Format JSON output using a Go template; implies --json (see gt help formatting)

--user="" Account name on the selected instance

$ gt issue unlock 12

gt-issue(1)

Nov 2026 gitea-cli