wastebin-mcp-go/docs/agents/issue-tracker.md
XLion b2dd244643
docs: fix documentation issues #3, #4, #5, #6
- mcp.go: fix password schema description (use Wastebin-Password header, not HTTP basic auth) [Closes #4]
- docs/MCP_TOOLS.md: correct error table to match actual code errors, add missing empty content entry [Closes #3]
- docs/INSTALL.md: fix WASTEBIN_MCP_BLOCKED_PATHS default and Go version minimum [Closes #6]
- docs/agents/issue-tracker.md: remove reference to non-existent pull-requests.md
- docs/agents/domain.md: fix stale directory tree (src/ -> actual structure) [Closes #5]
2026-06-17 02:46:56 +08:00

1.6 KiB

Issue tracker: GitHub

Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.

Conventions

  • Create an issue: gh issue create --title "..." --body "...". Use a heredoc for multi-line bodies.
  • Read an issue: gh issue view <number> --json number,title,body,labels,comments --jq '{number, title, body, labels: [.labels[].name], comments: [.comments[].body]}'
  • List issues: gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]' with appropriate --label and --state filters.
  • Comment on an issue: gh issue comment <number> --body "..."
  • Apply / remove labels: gh issue edit <number> --add-label "..." / --remove-label "..."
  • Close: gh issue close <number> --comment "..."

Infer the repo from git remote -v — gh does this automatically when run inside a clone.

Before applying or removing labels, read docs/agents/triage-labels.md. Labels accepted, needs-explain, and rejected are human-only decision labels; do not change them unless the user explicitly requests that exact label operation.

When a skill says "publish to the issue tracker"

Create a GitHub issue.

When a skill says "fetch the relevant ticket"

Run gh issue view <number> --json number,title,body,labels,comments --jq '{number, title, body, labels: [.labels[].name], comments: [.comments[].body]}'.

Pull requests

PR agents must ignore REPORT.md unless explicitly asked for a local report, and every PR body must mention related documentation updates or explain why none were needed.