Defame1297
bbc73008a3
Generated output, not authored content: scripts/sync-plugin-content.sh --all. Claude Code has no .apm/ awareness, so this compiled mirror must track .apm/ or the check-plugin-content-sync pre-push hook reports drift. Deferred to a single commit at the end of the wave on purpose. sync_dir runs rm -rf before every copy, so running it while seven agents were editing the same plugin would have raced them; agents were told not to sync for that reason. Refs #99
49 lines
2.5 KiB
Markdown
49 lines
2.5 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:** (tool parameters and SHA/concurrency behavior cross-checked live against the deployed MCP tool schemas via ToolSearch)
|
|
- SKILL.md (Gotchas — cross-flow parameter and encoding traps; Dispatch)
|
|
- references/reading.md (read-tool parameters, `ref`/`tree_sha` selection, tree pagination)
|
|
- references/writing.md (write-tool parameters, SHA/concurrency behavior, canonical call sequences, failed-write triage)
|
|
|
|
## 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 — base64 response encoding)
|
|
- references/reading.md (top-level `sha` field location, `get_dir_contents`/`get_repository_tree` not being usable SHA sources for a file write)
|
|
- references/writing.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 (Handoff — committing straight to a branch is the normal path, not an escape hatch)
|
|
|
|
## 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)
|