heavy-duty/ceremony
7
0
Fork 2
Code Issues 1 Pull requests Projects Releases 8 Packages Wiki Activity Actions

Merge pull request #296 from andriujoseba/build/264-flagging-unassigned

Browse source 
docs(triage): scope no-assignee bug to flagging
This commit is contained in:
Daniel Marin 2026-08-04 14:39:59 +01:00 committed by GitHub
commit f899bb5690
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
TRIAGE.md
View file

@ -70,8 +70,8 @@ is the failure this whole flow exists to prevent.
when that ruling or any directive or answered builder question delivers
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`.
when the comment lives there. Flagging 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`.
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

4
changelog.d/264.md Normal file
View file

@ -0,0 +1,4 @@
### Changed
- TRIAGE.md now scopes the no-assignee board bug to flagging an unassigned
issue, while still directing triage to repair ownership instead (#264).