Defame1297
be9b8d277f
gitea-files' always-loaded Gotchas said "content is base64 both ways" without qualification. The `main` text carried an exception for `withLines: true` and both halves were dropped. Verified live: `get_file_contents` with `withLines: true` returns plain JSON text while the same response still reports `"encoding":"base64"`. An agent that follows the recommendation two sentences later and applies the unconditional decode gets garbage, with the response's own field confirming the wrong answer. Exception restored, and the lying field named. gitea-orchestrate was never updated for `rename_branch`: absent from the operation enum, so an agent caller got "unknown operation", and absent from the destructive-confirm list, though branches.md requires a rename with open PRs or a protection rule to be confirmed exactly as `delete_branch` is. Added to both — the confirm gate rather than the enum alone, because accepting the operation without it routes around a rule the skill states while appearing to support it. The compatibility frontmatter, which the agent reads, still omitted the tool too. Two more always-loaded Gotchas contradicted their own reference files, and the Gotcha was wrong both times: issues and PRs are distinguishable on a list item by the `html_url` path segment (confirmed live — #129 at /pulls/, #128 at /issues/), and `get_repository_tree` takes `tree_sha`, not `ref`. `review_comments` was asserted as unconditionally present on the PR get response. It is absent on a PR with no review comments, so the claim is downgraded to present-when-non-zero rather than stated as response shape. The label-exclusivity relocation moved the rule out of label-inference.md and into labels.md without updating sources.md, leaving the one rule in this branch that writes differently to live repos citing a file that no longer carries it. The rule itself is correct as it stands and `main` was wrong — every Kind/* label on this instance is exclusive:false, every Priority/* and Status/* is true — so only the provenance record is corrected. Routing: gitea-workflow lost the human-caller discriminator and widened from status checks to any request, which sent "close #42" to a branch that resolves the number and presents detail without ever closing it. gitea-branches and gitea-issues regain trigger phrasings the retrofit dropped. Refs: #92
4.6 KiB
4.6 KiB
name, description, compatibility, metadata, allowed-tools
| name | description | compatibility | metadata | allowed-tools | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| gitea-issues | Use when reading or writing Gitea issues — "create an issue", "what issues are open", "close issue #N", "comment on issue #N", "label issue #N", "search issues for X" — even when the user does not say "Gitea". Not pull requests -> `gitea-prs`. Not label or milestone definitions -> `gitea-labels-milestones`. | Requires Gitea MCP server configured with write:issue and write:repository token scopes. Requires git remote "origin" pointing to the Gitea instance for owner/repo resolution when invoked directly by a human; an orchestrating caller (e.g. gitea-workflow) may pass owner/repo already resolved. |
|
Bash mcp__gitea__list_issues mcp__gitea__issue_read mcp__gitea__issue_write mcp__gitea__search_issues |
Gotchas
list_issuesmixes in PRs unless you filter. Issues and PRs share one number space; passtype: "issues"to exclude PRs (or"pulls").is_pullis returned only byissue_read method: "get"— on a list item the only tell ishtml_url's path segment (/issues/vs/pulls/).- Label IDs and names are not interchangeable.
issue_writetakes numeric IDs only;list_issuesandsearch_issuesfilter by name;issue_read "get"returns names but"get_labels"returns full objects with IDs. Resolve viagitea-labels-milestonesunless the caller named exact labels. - A merge does not itself close the issue. Gitea has no close-on-merge event, but a
Fixes #Nin the merged commits can, depending on merge style (gitea-prs). Re-read its state after a merge before closing it manually. - A 404 may really be a 403. Gitea hides permission errors as not-found — check the token's
write:issuescope before concluding the issue does not exist.
Step 1 — Resolve owner and repo
An orchestrating caller may pass owner and repo in already, and the search row is cross-repository and needs only a query — both skip this step. Otherwise, before any tool call:
git remote get-url origin
If origin is unset 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
One invocation takes one row. Read only the reference(s) that row names — the call signatures were verified against the live MCP schema and differ from the published API docs in ways the body does not restate.
| Invocation | Flow | Read |
|---|---|---|
/gitea-issues or /gitea-issues list |
List issues with type: "issues" so PRs are excluded, optionally filtered by state |
references/issues.md |
/gitea-issues <N> |
Get one issue, routing to gitea-prs when the number turns out to be a PR |
references/issues.md |
/gitea-issues <N> comments |
Get an issue's comments | references/issues.md |
/gitea-issues <N> labels |
Get an issue's labels as full objects, IDs included | references/issues.md |
/gitea-issues close <N> |
Close an issue by updating its state | references/issues.md |
/gitea-issues comment <N> |
Add a comment drawn from conversation context, never one invented to fill the gap — a comment on a live issue is not cheap to undo | references/issues.md |
/gitea-issues label <N> |
Apply, replace or remove labels using IDs resolved by gitea-labels-milestones |
references/issues.md |
/gitea-issues create |
Create an issue — Step 3 first | references/enrichments.md, then references/issues.md |
/gitea-issues search <query> |
Cross-repo search, narrowed by owner, state, type or labels | references/search.md |
Step 3 — Create
Only the create flow reaches this step.
- Take
titleandbodyfrom conversation context — the most recent task, bug report, or explicit statement. An empty body is an acceptable fallback, an invented one is not. - Run the enrichments in
references/enrichments.md, then create with the resolved IDs perreferences/issues.md. Omitting a parameter always beats guessing its value — a wrong milestone or assignee is harder to notice than a missing one. - Fire immediately, with no confirmation step. A create is cheap to undo by closing, so a gate here only costs a round trip.
Step 4 — Report
Reads: a compact table or numbered list — number, title, state, labels, milestone.
Writes: what was created or updated, with the issue number and the URL when one is returned.
Errors: the HTTP code and message as returned, without paraphrasing either.