SKILL.md's headline Gotcha said `list_issues` "has no `type` filter", and references/issues.md stated in bold that neither `type` nor `milestones` exists, "despite both appearing in api-reference.md". Both parameters are present on the deployed gitea-mcp v1.7.0 and both work: `type: "issues"` returns only issues, `type: "pulls"` only PRs, and `milestones` filters by name. Unfiltered, the same window returns them interleaved, so the mixing the Gotcha describes is real — only the stated remedy was wrong. This mattered most in gitea-workflow's no-args check-in, which lists open issues through this skill and so reported PRs under "Open Issues" while the skill forbade the one-parameter fix. The list flow now passes `type: "issues"`. references/sources.md recorded the absence as a live-verification win over stale research docs; it now records that the earlier check was superseded by v1.7.0, since drift runs in both directions. gitea-prs cited the same parameter as its canonical drift example and no longer does — no replacement example was substituted, because the obvious candidate was not verified in this pass. Also defaults label writes to `add_labels`: `replace_labels` clears every label not in the array, and per-label exclusivity makes blanket replacement destructive for a non-exclusive scope. Verified live against gitea-mcp v1.7.0, read-only calls. Refs #99
2.7 KiB
2.7 KiB
Sources
Note on call signatures: per docs/adr/0011-gitea-skill-deep-modules.md, the tool parameter
signatures in references/issues.md and references/search.md are re-verified live via
ToolSearch against the deployed gitea-mcp server — they are not copied verbatim from
api-reference.md. 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. That re-verification is
ongoing, not one-off: an earlier live check recorded list_issues as lacking the type and
milestones parameters api-reference.md documents, and both are present on the deployed
gitea-mcp v1.7.0, which is the version these signatures are current as of.
gitea-mcp-repo
- URL: https://gitea.com/gitea/gitea-mcp
- Description: Official gitea-mcp repository (v1.3.0); operation/*.go source files documenting all 55 MCP tools, their parameters, and CLI flags.
- Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
- Contributing files: SKILL.md, references/issues.md, references/search.md, references/enrichments.md
- Status:
extracted
gitea-mcp-slim-go
- URL: https://gitea.com/gitea/gitea-mcp/raw/branch/main/operation/issue/slim.go
- Description: Slim response shape structs from gitea-mcp source; defines exactly which fields the MCP server returns for issues (label name-vs-ID slimming, milestone object-vs-string shape,
is_pullpresence on single-item reads only). - Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
- Contributing files: SKILL.md, references/issues.md
- Status:
extracted
context7-websites-gitea
- URL: context7:/websites/gitea
- Description: Official Gitea docs mirror on Context7 (docs.gitea.com content) — backs the automatic cross-reference rendering (
#N/!N) that validates the "Depends on #N" dependency-linking convention. - Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
- Contributing files: references/enrichments.md
- Status:
extracted
context7-gitea-tea-cli
- URL: context7:/git_gitea_com/gitea_tea
- Description: Official
teaCLI (reference Gitea client) docs on Context7 — practitioner command patterns for issues, PRs, and releases. Consulted alongside context7-websites-gitea while researchingworkflow-conventions.md's cross-reference-linking section (both sources contribute to that research doc); its issue-specific command patterns did not end up informing any gitea-issues content beyond what context7-websites-gitea already backs. - Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
- Contributing files: (none)
- Status:
extracted