Defame1297
d09375556a
A documentation-accuracy audit against research docs found three gotchas in troubleshooting.md that were dropped from gitea-files/SKILL.md during original authoring: signed-commit branch protection silently blocking file writes (a distinct failure mode from stale-SHA that an agent could otherwise misdiagnose and retry indefinitely), reverse-proxy 413s on large base64-encoded write payloads, and 404-vs-403 scope masking on the read tools. Also adds the context7-gitea-tea-cli provenance entry to references/sources.md (Contributing files: none) to resolve a pre-existing skill-audit provenance FAIL surfaced while validating this change, matching the pattern already used by sibling skills. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VwtxcDXuLZxYzWnT2FaoZU
47 lines
2.2 KiB
Markdown
47 lines
2.2 KiB
Markdown
# Sources
|
|
|
|
## gitea-mcp-repo
|
|
|
|
**Description:** Official gitea-mcp repository (v1.3.0); operation/*.go source files documenting all 55 MCP tools, their parameters, and CLI flags.
|
|
|
|
**Source:** https://gitea.com/gitea/gitea-mcp
|
|
|
|
- **Research doc:** plugins/gitea/docs/research/docs/gitea/sources.md
|
|
|
|
**Contributing files:**
|
|
- SKILL.md (Gotchas, Reading, Writing — tool parameters and SHA/concurrency behavior, cross-checked live against the deployed MCP tool schemas via ToolSearch)
|
|
- references/examples.md (canonical call sequences)
|
|
|
|
## gitea-mcp-slim-go
|
|
|
|
**Description:** Slim response shape structs from gitea-mcp source; defines exactly which fields the MCP server returns for files (top-level `sha`, no nested `content.sha`) and directory/tree entries.
|
|
|
|
**Source:** https://gitea.com/gitea/gitea-mcp/raw/branch/main/operation/repo/slim.go
|
|
|
|
- **Research doc:** plugins/gitea/docs/research/docs/gitea/sources.md
|
|
|
|
**Contributing files:**
|
|
- SKILL.md (Gotchas — top-level `sha` field location, `get_dir_contents`/`get_repository_tree` not being usable SHA sources for a file write)
|
|
- references/examples.md (SHA-first update/delete sequences)
|
|
|
|
## context7-websites-gitea
|
|
|
|
**Description:** Official Gitea docs mirror on Context7 (docs.gitea.com content) — confirms direct-commit file editing through the web UI is a first-class, expected workflow rather than an API-only escape hatch.
|
|
|
|
**Source:** context7:/websites/gitea
|
|
|
|
- **Research doc:** plugins/gitea/docs/research/docs/gitea/sources.md
|
|
|
|
**Contributing files:**
|
|
- SKILL.md (Gotchas — "Direct commits to a branch are a first-class action, not a workaround")
|
|
|
|
## context7-gitea-tea-cli
|
|
|
|
**Description:** Official `tea` CLI (reference Gitea client) docs on Context7 — practitioner command patterns for issues, PRs, and releases, including semver tag/release conventions, draft/prerelease flags, and release-notes-from-file conventions. Consulted alongside `context7-websites-gitea` while researching `workflow-conventions.md` (both sources contribute to that research doc, backing `gitea-workflow`); its file-command patterns did not end up informing any gitea-files content.
|
|
|
|
**Source:** context7:/git_gitea_com/gitea_tea
|
|
|
|
- **Research doc:** plugins/gitea/docs/research/docs/gitea/sources.md
|
|
|
|
**Contributing files:** (none)
|