GT-PR-REVIEW-REPLY(1) gitea-cli Manual GT-PR-REVIEW-REPLY(1)

gt-pr-review-reply - Reply to an inline review comment

gt pr review reply <number> <comment-id> [flags]

Reply to an inline review comment

A pull request can be supplied as argument in any of the following formats:
- by number, such as "13" or "#13"
- by URL, such as "https://gitea.com/OWNER/REPO/pulls/13"
- by the name of its head branch, such as "feature/login" or "bob:feature/login"; a branch that
  reads as OWNER/REPO#N, such as "fix/login#2", needs the OWNER:BRANCH form

author, body, created_at, id, line, old_line, path, resolver, review_id,
updated_at, url

-b, --body="" Reply body

-F, --body-file="" Read the body from file, or - for stdin

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

-e, --editor[=false] Write the reply in your editor

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

--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 pr review reply 13 36 -b "Done, the password is hashed now"

gt-pr-review(1)

Nov 2026 gitea-cli