forked from heavy-duty/ceremony
b3b9830700
Merging #143 auto-closed #137 with a post-merge criterion unmet: the PR carried Closes #137 as doctrine required, the criterion could only be checked after the merge, and the contract was silent on the disagreement between GitHub's keyword and the pipeline's close authority — the same disagreement the cross-repo carve-out already resolved, one case over. BUILDER.md gains the second exception beside the first: when the issue body marks a criterion post-merge, the same-repo PR uses Refs #N and triage closes by hand on the evidence. TRIAGE.md makes the criterion carry its own mechanism; REVIEWER.md lists Refs #N as a spec pointer and stops treating the reference-only PR as a defect; CONTRIBUTING.md points at the one home instead of restating. No machinery, no label (#151 D5). Closes #151 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
11 lines
653 B
Markdown
11 lines
653 B
Markdown
### Changed
|
|
|
|
- Doctrine names the second `Closes #N` exception: a same-repo PR whose
|
|
authorizing issue marks an acceptance criterion post-merge uses `Refs #N`,
|
|
and triage closes the issue by hand on the evidence — merging #143
|
|
auto-closed #137 with exactly such a criterion unmet, and no role had been
|
|
told otherwise. TRIAGE.md now requires a post-merge criterion to carry its
|
|
own mechanism (post-merge, triage closes, `Refs #N`), REVIEWER.md lists
|
|
`Refs #N` beside `Closes #N` and `Part of <owner>/<repo>#N` and stops
|
|
treating the reference-only PR as a defect, and CONTRIBUTING.md points at
|
|
BUILDER.md as the rule's one home (#151).
|