Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity
Files
be9b8d277fefad8740f00e4753b653a5211d9141
holocron/plugins/gitea/skills/gitea-labels-milestones/references/sources.md
Defame1297 be9b8d277f fix(gitea): restore the withLines exception and route rename_branch through the orchestrator 
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
2026-09-01 12:38:53 +00:00

1.9 KiB
Raw Blame History

Sources

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/labels.md, references/milestones.md, references/label-inference.md
  • Status: extracted

gitea-mcp-slim-go

context7-websites-gitea

  • URL: context7:/websites/gitea
  • Description: Official Gitea docs mirror on Context7 (docs.gitea.com content) — scoped/exclusive label conventions and milestone/label state-transition semantics
  • Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
  • Contributing files: SKILL.md, references/labels.md, references/label-inference.md
  • Status: extracted

context7-gitea-tea-cli

  • URL: context7:/git_gitea_com/gitea_tea
  • Description: Official tea CLI (reference Gitea client) docs on Context7 — practitioner command patterns for labels and milestones
  • Research doc: plugins/gitea/docs/research/docs/gitea/sources.md
  • Contributing files: SKILL.md
  • Status: extracted
Reference in New Issue View Git Blame Copy Permalink