Defame1297
1a971ee003
gitea-issues asserted flatly that a merge never closes an issue, contradicting gitea-prs' references/merging.md, which documents that closing keywords in commits landing on the default branch do close one. The qualifier that made the claim true had been deleted; both sides now agree. gitea-releases had lost an epistemic hedge and its verification step, leaving conventions.md asserting unconfirmed tag auto-creation as fact. Nothing in the research corpus sources it, so the hedge and the verify-afterward instruction are back rather than upgraded. Descriptions were cut 50-240 chars under the 400 budget and shed routing with them: gitea-workflow's boundary named no target, gitea-prs lost the issue/PR number-space directive the suite is built around at 163/400, gitea-releases lost its boundary and every trigger. Restored, inside budget. Also restores delete_branch's hard-refusal strength and gitea-files' Read/Write/Edit pointer. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EJJrm5YmacbwMdzZpXcoti
60 lines
3.1 KiB
Markdown
60 lines
3.1 KiB
Markdown
---
|
|
name: gitea-branches
|
|
|
|
description: >
|
|
Use when listing, creating, renaming, or deleting branches in a Gitea repository,
|
|
or reading its commit history — even when the user does not say "Gitea". Not a
|
|
local checkout's branches -> `git-branches`. Not local history ->
|
|
`git-history`. Not a PR's head or base -> `gitea-prs`.
|
|
|
|
compatibility: Requires Gitea MCP server configured with a token with write:repository scope; this is confirmed to gate list_branches, create_branch, and delete_branch (Gitea gates reads behind write scope for repo-scoped operations), and is inferred by analogy (not explicitly confirmed by source docs) to also gate list_commits and get_commit. Requires git remote "origin" pointing to the Gitea instance.
|
|
|
|
metadata:
|
|
category: integration
|
|
version: "0.1.2"
|
|
source_keys:
|
|
- gitea-mcp-repo
|
|
- gitea-mcp-slim-go
|
|
- context7-websites-gitea
|
|
|
|
allowed-tools: Bash mcp__gitea__list_branches mcp__gitea__create_branch mcp__gitea__rename_branch mcp__gitea__delete_branch mcp__gitea__list_commits mcp__gitea__get_commit
|
|
---
|
|
|
|
## Gotchas
|
|
|
|
- **404 often means 403.** Gitea masks permission errors as not-found; on an unexpected one, check token scope before reporting a branch or commit missing.
|
|
- **Nothing auto-paginates.** `list_branches` and `list_commits` return one page; iterate `page` until the returned count is below `per_page`.
|
|
- **`delete_branch` has no force-push guard.** Treat deleting a protected branch as a hard refusal unless the user explicitly confirms it in the conversation. Check `protected` from `list_branches` first — a protected branch need not be named `main`.
|
|
|
|
## Step 1 — Resolve owner and repo
|
|
|
|
Before any tool call, extract `owner` and `repo` from the git remote:
|
|
|
|
```bash
|
|
git remote get-url origin
|
|
```
|
|
|
|
`get_me` and `list_my_repos` are blocked under the token scope this skill assumes, so the remote is the only source. If origin is not set or the URL is not a Gitea URL, stop and report: "No Gitea remote found — set origin to your Gitea instance URL."
|
|
|
|
## Step 2 — Dispatch
|
|
|
|
| Invocation | Action |
|
|
|---|---|
|
|
| `/gitea-branches` or `/gitea-branches list` | List branches |
|
|
| `/gitea-branches create <name> [from <base>]` | Create branch |
|
|
| `/gitea-branches rename <name> to <new-name>` | Rename branch |
|
|
| `/gitea-branches delete <name>` | Delete branch |
|
|
| `/gitea-branches commits [on <branch>] [touching <path>]` | List commit history |
|
|
| `/gitea-branches commit <sha>` | Get full detail for one commit |
|
|
|
|
For branch operations (list/create/rename/delete), read `references/branches.md` — it carries the call signatures, the `old_branch` source rule, and the protected-branch refusal in full.
|
|
For commit operations (list/get), read `references/commits.md`.
|
|
|
|
## Step 3 — Report
|
|
|
|
For reads: display branches as name + protected flag; display commits as SHA (short), message summary, author, date.
|
|
|
|
For writes (create/rename/delete): confirm the action taken, the branch name, and (for create) the base it forked from or (for rename) the name it had before.
|
|
|
|
For errors: surface the HTTP code and message, applying the 404 gotcha above before reporting "not found" to the user.
|