Skip to content

Title the catch-all release-notes category for what it holds - #3029

Merged
tanem merged 1 commit into
masterfrom
release-notes-patch-category
Aug 8, 2026
Merged

Title the catch-all release-notes category for what it holds#3029
tanem merged 1 commit into
masterfrom
release-notes-patch-category

Conversation

@tanem

@tanem tanem commented Aug 8, 2026

Copy link
Copy Markdown
Owner

Most weeks release nothing but patches, so "Everything Else" ends up the only heading in the generated notes — and a heading that defines itself by contrast reads as a mistake when there is nothing to contrast it with.

"Fixes & Maintenance" reads alone and reads as the third of three. It is also the more honest name: under the label convention every PR that falls through to the catch-all is a patch, so this was never a junk drawer for uncategorised work.

Showing the heading only when the other two are populated is not expressible here. GitHub evaluates this file identically every release, so a conditional heading would mean generating the notes by hand rather than letting GitHub write them. Dropping the catch-all instead is worse: without * GitHub omits the unmatched pull requests from the notes entirely, which on a patch-only week is all of them.

Cosmetic and forward-only — already-published releases keep the heading they were generated with.

Most weeks release nothing but patches, so "Everything Else" ends up
the only heading in the generated notes — and a heading that defines
itself by contrast reads as a mistake when there is nothing to
contrast it with.

"Fixes & Maintenance" reads alone and reads as the third of three. It
is also the more honest name: under the label convention every PR that
falls through to the catch-all is a patch, so this was never a junk
drawer for uncategorised work.

Showing the heading only when the other two are populated is not
expressible here. GitHub evaluates this file identically every
release, so a conditional heading would mean generating the notes
by hand rather than letting GitHub write them. Dropping the catch-all
instead is worse: without `*` GitHub omits the unmatched pull requests
from the notes entirely, which on a patch-only week is all of them.
@tanem tanem added the internal label Aug 8, 2026
@tanem
tanem merged commit 5196836 into master Aug 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant