Defame1297
8680adf4c0
gitea-releases was the weakest skill in the plugin: no allowed-tools, no owner/repo resolution, and a checkbox list where a dispatch table belongs, so an agent reaching it had to guess both its permissions and its inputs. The id-vs-tag_name trap — deleting by tag name where the API wants the numeric id — is restored as an explicit Gotcha because it destroys the wrong release silently. Elsewhere the `exclusive` flag was documented on the wrong side of the read/write split, and label data from one instance was presented as though it were universal, which invites an agent to assume a taxonomy that does not exist on the target repo. rename_branch was missing from the branch surface. Reference prose and fences are cleaned up in passing.
42 lines
2.9 KiB
Markdown
42 lines
2.9 KiB
Markdown
# Sources
|
|
|
|
**Note on call signatures:** per `docs/adr/0011-gitea-skill-deep-modules.md`, the tool parameter
|
|
signatures in `references/branches.md` and `references/commits.md` were re-verified live via
|
|
`ToolSearch` against the deployed `gitea-mcp` server — **last verified against v1.7.0**, as reported
|
|
by `get_gitea_mcp_server_version` — rather than copied verbatim from `api-reference.md` below. This resolves issue #6 comment #849's root-cause finding
|
|
that a prior skill was authored from API docs that had drifted from the actual MCP tool schema.
|
|
The research docs cited here informed gotchas, response shapes, and workflow context, not the
|
|
parameter lists themselves.
|
|
|
|
## gitea-mcp-repo
|
|
|
|
- **URL:** https://gitea.com/gitea/gitea-mcp
|
|
- **Description:** Official gitea-mcp repository; operation/*.go source files documenting the MCP tools, their parameters, and CLI flags. Extracted at v1.3.0; the parameter lists carried into this skill are re-verified live against the deployed server, last at v1.7.0. Informed the dispatch table and pagination / 404-may-mean-403 gotchas in SKILL.md, and the list/create/delete branch and list/get commit mechanics (including 409 conflict and default-branch fallback behavior) in references/branches.md and references/commits.md.
|
|
- **Research doc:** plugins/gitea/docs/research/docs/gitea/sources.md
|
|
- **Contributing files:** SKILL.md, references/branches.md, references/commits.md
|
|
- **Status:** `extracted`
|
|
|
|
## gitea-mcp-slim-go
|
|
|
|
- **URL:** https://gitea.com/gitea/gitea-mcp/raw/branch/main/operation/repo/slim.go
|
|
- **Description:** Slim response shape structs from gitea-mcp source, extracted at v1.3.0; defines exactly which fields the MCP server returns for branches (name, protected, commit_sha) and commits (sha, html_url, created, message, author), and informed get_commit's always-populated guarantee vs. list_commits' conditional fields.
|
|
- **Research doc:** plugins/gitea/docs/research/docs/gitea/sources.md
|
|
- **Contributing files:** references/branches.md, references/commits.md
|
|
- **Status:** `extracted`
|
|
|
|
## context7-websites-gitea
|
|
|
|
- **URL:** context7:/websites/gitea
|
|
- **Description:** Official Gitea docs mirror on Context7 — informed the protected-branch gotcha in SKILL.md (protected branches can block server-side operations regardless of client-side checks; admins aren't exempt by default).
|
|
- **Research doc:** plugins/gitea/docs/research/docs/gitea/sources.md
|
|
- **Contributing files:** SKILL.md
|
|
- **Status:** `extracted`
|
|
|
|
## context7-gitea-tea-cli
|
|
|
|
- **URL:** context7:/git_gitea_com/gitea_tea
|
|
- **Description:** Official `tea` CLI docs on Context7 — practitioner conventions for issues, PRs, and releases (semver tags, draft/prerelease flags). Consulted as part of the shared research pass but its content is scoped to releases/tags, out of scope for branches/commits — no content from it was used in this skill.
|
|
- **Research doc:** plugins/gitea/docs/research/docs/gitea/sources.md
|
|
- **Contributing files:** (none)
|
|
- **Status:** `extracted`
|