Get a commit
get_commitFetch a single commit by owner/repo/SHA to inspect its details and signature verification status, including verified, unverified, or unsigned.
Instructions
Get one commit (owner/repo/sha), slimmed to the same fields as list_commits. Use it to check whether a commit was signed and whether the forge could verify it: signature is "verified", "unverified" or "unsigned", with signer on a verified one and reason (a gpg.error.* key) on an unverified one. Note that Gitea reports gpg.error.no_gpg_keys_found both for a key it does not hold and for one it holds but has not verified, so that reason does not distinguish the two.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"owner": "<owner>",
"repo": "<repo>",
"sha": "<sha>"
},
"name": "get_commit"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sha | Yes | The commit to fetch. A full id is safest; a branch or tag name also resolves. | |
| repo | Yes | Repository name. | |
| owner | Yes | Repository owner — user or organization. |