Files

Defame1297 bbc73008a3 chore(gitea): regenerate the flat content mirror after the ADR-0020 retrofit

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

2026-08-30 12:42:20 +00:00

1.3 KiB

Raw Blame History

topic, source_keys

topic

source_keys

number-resolution

gitea-mcp-repo

gitea-mcp-slim-go

context7-websites-gitea

Resolving a bare issue-or-PR number

The user has referenced a bare number without saying "issue" or "PR" (e.g. "what's going on with #42"). Resolve it with a real call — never dispatch to gitea-issues or gitea-prs by guessing from phrasing alone, because "that sounds like a bug" is not evidence and the two domains share one number space.

Invoke gitea-issues to run issue_read method: "get" on that number.
Check the response's is_pull field:
- true → it's a PR. Invoke gitea-prs for full PR detail (status, diff, reviews as appropriate to the request) and present that instead.
- false or absent → it's an issue. Present the issue detail already retrieved.
If the resolution call 404s, don't conclude the number doesn't exist. Gitea hides permission errors as not-found (documented in gitea-issues' Gotchas), so report the 404 and suggest verifying the token carries write:issue rather than reporting "no such issue or PR."

Then report per SKILL.md's Report section, saying which domain the number turned out to be before showing detail ("That's a pull request:" / "That's an issue:") — otherwise the user cannot tell the resolution happened.

1.3 KiB Raw Blame History

Resolving a bare issue-or-PR number

1.3 KiB

Raw Blame History