Repository navigation
ci: categorized release notes via auto-labeling - #10
Merged
Merged
Conversation
Add .github/release.yml so `gh release create --generate-notes` groups merged PRs into categories (Breaking/Features/Bug Fixes/Performance/ Documentation/Maintenance & CI/Other). GitHub categorizes strictly by PR label, so add a label-pr workflow that maps Conventional Commit title prefixes (feat/fix/perf/docs/refactor/chore/ci/...) to the labels those categories key off, including breaking-change for `!`/BREAKING CHANGE markers. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Make GitHub's auto-generated release notes (already used by
release.ymlviagh release create --generate-notes) produce a categorized changelog instead of a flat "What's Changed" list..github/release.yml— groups merged PRs into 🛠 Breaking / 🎉 Features / 🐛 Bug Fixes / ⚡ Performance / 📚 Documentation / 🧹 Maintenance & CI / 📦 Other. Excludes bot PRs and anything labeledskip-changelog..github/workflows/label-pr.yml— GitHub categorizes strictly by PR label, but this project encodes change type in Conventional Commit titles. This workflow bridges the gap: it reads the title prefix and applies the matching label (feat→enhancement,fix→bug,perf→performance,docs→documentation,refactor/chore/ci/build/style/test→maintenance,!/BREAKING CHANGE→breaking-change).Also created the three new labels the config references:
performance,maintenance,breaking-change.Notes
github-scriptJS context (not${{ }}in a shellrun:), so there's no command-injection vector.pull_request_targetis used so fork PRs can be labeled; the PR's code is never checked out.maintenance.🤖 Generated with Claude Code