Repository navigation
docs: describe how agents work on issues and keep the project current - #553
olebhansen-agent wants to merge 5 commits into
Conversation
Agents missed pull requests that already existed for an issue, and nothing told people who was on an issue or what it waited for. AGENTS.md now says how far an agent takes an issue on its own, by the issue's type, how to find and link the work, and how to keep the digdir-agents project current. The project has no status for released work, so the release steps archive what a release shipped. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
|
GitHub sets Waiting to be released on every closed item, also one that no release will ship. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
This waits for a code owner's approval, since CODEOWNERS gives The one thing to weigh before approving is under Risk: agents will take reproducible bugs and enhancements from Inbox to merged without asking first. |
A pull request that lacks only a code owner's approval was set to Up-for-grabs in Testing, though no session can move it on. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
Since the comment above, the rules say to open every pull request as a draft and to assign yourself to work you follow up while another agent does it. The evidence now covers the issue commands, which were run when the rules were applied to the board. It waits for a code owner's approval again. Nothing else is open. |
…ollow up Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
Since the last comment, three things changed after input from the code owner:
It waits for a code owner's approval. Nothing else is open. |
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Summary
AGENTS.mdgets a section on working on issues. It replaces #545.no-agentissues alone.Closes #Nin the description, and record sub-issues and blocked-by as relations. Assign yourself to what you work on and to what you follow up while another agent works on it.CONTRIBUTING.mdgets a release step that archives what the release shipped, since the project has no status after Waiting to be released.Checks show that a change works, not that the project should have it. That is why the type sets the threshold, and why a Feature stops for a person even when it is easy to build.
Evidence
#539 repeated the change in the draft #533 for #532, and was closed as a duplicate. #538 was missing from #537's Development section until
Closes #537was added to its description.gh issue view 532 --json closedByPullRequestsReferenceslists #533.Against project 74,
gh project item-edit 74 --owner digdir --url URL --field Status --value Testingset the field on this pull request and printed the item's id, and--clearcleared WIP State on another. Closing #545 without a merge moved it to Waiting to be released, andgh project item-archive 74 --owner digdir --id IDtook it off the board.The rules were applied to the 121 items on the board.
gh issue editset the type on 78 issues,--parentmade #298 a sub-issue of #338, and--add-blocked-bywith a URL made #524 blocked by digdir/microsandbox#20 in another repository.Not confirmed: whether GitHub adds an archived pull request to the project again when it changes. #545 stayed archived when its branch was deleted.
Risk
🤖 Generated with Claude Code