docs(agents): declare GitHub Issues as this repo's tracker - #17
Conversation
Repo had no docs/agents/issue-tracker.md, so nothing declared where multi-session work gets tracked. Needed before filing the confirmed Kimi Code skills-shelf misattribution bug. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: daf89248e8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| No special label taxonomy yet — use plain, descriptive titles and let labels | ||
| emerge as the issue count grows. Triage/claim discipline follows the | ||
| workspace-wide protocol: `~/Developer/ecosystem-alignment/docs/agents/github-work-protocol.md`. |
There was a problem hiding this comment.
In a fresh or public clone, ~/Developer/ecosystem-alignment/docs/agents/github-work-protocol.md is outside this repository and may not exist (it is also absent from the current workspace), so contributors and agents cannot follow the newly declared triage/claim process. Link to a public document or include a repository-relative copy instead. This is particularly important because the project contract defines this as a standalone public repository.
AGENTS.md reference: AGENTS.md:L22-L26
Useful? React with 👍 / 👎.
1 participant
Summary
docs/agents/issue-tracker.mddeclaring GitHub Issues as devcat-cli's authoritative tracker, per the workspace's New-Projects convention (every repo should have this from day one).Test plan