GT-ISSUE-COMMENT-CREATE(1) gitea-cli Manual GT-ISSUE-COMMENT-CREATE(1) NAME gt-issue-comment-create - Add a comment to an issue SYNOPSIS gt issue comment create { | } [flags] DESCRIPTION Add a comment to an issue 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. JSON FIELDS author, body, created_at, id, issue_number, updated_at, url OPTIONS --attachment=[] File to attach to the comment (repeatable) -b, --body="" Comment text -F, --body-file="" Read the comment from file, or - for stdin -e, --editor[=false] Write the comment in the configured editor -h, --help[=false] help for create OPTIONS INHERITED FROM PARENT COMMANDS --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) --user="" Account name on the selected instance EXAMPLE $ gt issue comment create 12 --body "Looks good" $ gt issue comment add 12 --editor SEE ALSO gt-issue-comment(1) gitea-cli Nov 2026 GT-ISSUE-COMMENT-CREATE(1)