Say that a free ADR number means free across open PRs too #45
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/adr-numbering-across-open-prs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two ADR number collisions today (0039, then 0043). In both cases each author correctly took "the next free number" from
main— and got the same answer, because neither branch had merged.Records that "next free" spans
mainplus every open PR, and that renumbering is forbidden only after a record lands onmain, where something might link to it. Before merge, renumbering the branch further from merging is the fix.Documentation only.
Verdict: mergeable
No contradiction with ADR-0001 — it already scopes "never renumber" to a record merged onto
main("This rule binds from the moment a record is merged ontomain"), so this change is a correct restatement, and actually tightens the README's previously unqualified "never renumber them" to match. Worth citing ADR-0001 here for that reason, the way the partial-supersession paragraph just below already does — right now the two texts state the same rule with no link between them.History check: the 0039 collision is well corroborated — ADR-0039 (Editor-delete-places) merged at 17:57 on 2026-08-04, and "Renumber password policy ADR to 0040" landed 16 minutes later, i.e. the not-yet-merged branch was the one renumbered, matching the guidance exactly. I could not find any commit evidence (message, or a second "Renumber…" commit) for the claimed 0043 collision — that doesn't mean it didn't happen (a collision caught before push leaves no separate trace), but it's the one claim in the PR body I can't independently confirm. Worth double-checking before merge since the whole point of the change is to be a reliable factual record.
Guidance is actionable as written ("check the open PRs... say in the PR body which number you took").