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

gt-issue-timeline - Show the activity on an issue

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

Show what happened on an issue, oldest first: comments, and changes such as labels, milestones, titles, assignees, references, logged time and state changes.

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.

assignee, assignee_team, author, body, created_at, deadline, dependent_issue,
duration, id, label, label_added, milestone, new_title, old_deadline,
old_milestone, old_title, removed_assignee, type, url

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

-L, --limit=30 Maximum number of results (1..1000)

--page=1 Result page

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

$ gt issue timeline 12
$ gt issue timeline 12 --json type,author,created_at

gt-issue(1)

Nov 2026 gitea-cli