table of contents
| GT-COMMIT-COMPARE(1) | gitea-cli Manual | GT-COMMIT-COMPARE(1) |
NAME¶
gt-commit-compare - List the commits that one ref has and another has not
SYNOPSIS¶
gt commit compare {<base>...<head> | <base> <head>} [flags]
DESCRIPTION¶
List the commits that <head> has and <base> has not: what a pull request from <head> into <base> would bring. Both are branches, tags or commits.
ARGUMENTS¶
A repository can be supplied as NAME (one of yours), OWNER/NAME, HOST/OWNER/NAME or a URL. Without an argument, the repository of the current Git clone is used.
JSON FIELDS¶
base, commits, head, total_commits
OPTIONS¶
-h, --help[=false] help for compare
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)
--template="" Format JSON output using a Go template; implies --json (see gt help formatting)
--user="" Account name on the selected instance
EXAMPLE¶
$ gt commit compare main...feature/login $ gt commit compare v1.1.0 v1.2.0 --json total_commits
SEE ALSO¶
| Nov 2026 | gitea-cli |