Defame1297
5854961c1f
Adds plugins/gitea/skills/gitea-branches/ per ADR 0011, covering list_branches/create_branch/delete_branch (migrated from the flat plugins/bin/skills/gitea/ dispatch) plus list_commits/get_commit (new read-only commit-history domain). Call signatures were re-verified live via ToolSearch against the deployed gitea-mcp server rather than copied from api-reference.md, per issue #6 comment #849's root-cause fix. Bumps the gitea plugin to 1.1.0 in both manifests for the new skill.
2.8 KiB
topic, source_keys
| topic | source_keys | ||
|---|---|---|---|
| branches |
|
Branch operations
Call signatures below were verified live against the deployed gitea-mcp server via ToolSearch
at authoring time, not copied from research docs — this is deliberate: research docs are generated
from source code at a point in time and can drift from the server actually deployed. Re-verify
against the live schema if these tools appear to behave differently than documented here.
list_branches
Parameters:
owner(string, required)repo(string, required)page(number, optional, default:1)per_page(number, optional, default:30)
Call:
list_branches owner: <owner> repo: <repo>
Response: one object per branch: name, protected (bool), commit_sha (present when the
underlying commit data is available).
Paginate if you need the full list (see Gotchas in SKILL.md) — iterate page until the returned
count is less than per_page.
create_branch
Parameters:
owner(string, required)repo(string, required)branch(string, required) — new branch nameold_branch(string, optional) — source branch; if omitted, defaults to the repo's default branch server-side (not necessarily your current local checkout)
Call:
create_branch owner: <owner> repo: <repo> branch: <new-name> old_branch: <source-branch>
Default dispatch: if the user gives a base ("branch off of X", "from X"), pass it as old_branch.
If they don't specify a base and you're mid-task on a local branch, pass your current branch
(git branch --show-current) as old_branch so the new branch forks from where you're actually
working, rather than silently falling back to the repo default. If neither applies (e.g. a fresh
top-level request with no working branch context), omit old_branch and let it default server-side.
A branch name collision returns 409 Conflict.
delete_branch
Parameters:
owner(string, required)repo(string, required)branch(string, required)
Call:
delete_branch owner: <owner> repo: <repo> branch: <name>
Before calling this, see the hard-refusal Gotcha in SKILL.md. If the target branch's name isn't
obviously a scratch/feature branch, call list_branches first and check protected on the
matching entry — name-matching main/master alone isn't authoritative, since a repo can protect
a differently-named default branch. Confirm explicitly with the user before deleting anything
protected, every time, regardless of how the request is phrased.
Token scope
list_branches works with write:issue alone. create_branch and delete_branch need
write:repository. All three are verified working empirically under a token with both scopes
(write:issue + write:repository).