codex-bot-andresmgsl/ceremony
1
0
Fork 0
forked from heavy-duty/ceremony
Code Pull requests Activity

docs: clarify attention target

Browse source
This commit is contained in:
Andriujose 2026-08-03 19:07:08 +00:00
parent 2e5aa52e29
commit dbb0554288
2 changed files with 9 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
TRIAGE.md
View file

@ -68,7 +68,10 @@ is the failure this whole flow exists to prevent.
agreement is reached, record the ruling as a decision in one comment, agreement is reached, record the ruling as a decision in one comment,
remove the label, and return the issue to its flow in that same comment; remove the label, and return the issue to its flow in that same comment;
when that ruling or any directive or answered builder question delivers when that ruling or any directive or answered builder question delivers
the assignee's next move in prose, set `attention` in the same comment. the assignee's next move in prose, set `attention` in the same comment on
the assigned issue that owns the claim — never on the pull request, even
when the comment lives there. An unassigned issue is a board bug, not a
demand; repair the board rather than setting `attention`.
This is not a substitute for minting work or for `needs-ruling`. This is not a substitute for minting work or for `needs-ruling`.
4. **Decline.** Real idea, wrong repo or wrong time. Say why plainly, link 4. **Decline.** Real idea, wrong repo or wrong time. Say why plainly, link
where it belongs if anywhere, close. A refusal with reasons is a good where it belongs if anywhere, close. A refusal with reasons is a good

5
changelog.d/230.md Normal file
View file

@ -0,0 +1,5 @@
### Fixed
- Triage now puts `attention` on the assigned issue that owns a claim, never
on its pull request, and treats an unassigned issue as a board bug rather
than a demand (#230).