docs(triage): scope no-assignee bug to flagging
This commit is contained in:
parent
4e0c5c2568
commit
5ea59780b6
2 changed files with 6 additions and 2 deletions
|
|
@ -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
4
changelog.d/264.md
Normal 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).
|
||||
Loading…
Reference in a new issue