docs: Capitalize PR title summary for changelog#2145
Merged
Conversation
Release Drafter strips the Conventional-Commit prefix, so the summary becomes the first word in the changelog. Lowercase summaries (CC's default) render as "add X"; capitalize so it reads "Add X". `replacers` can find/replace but cannot transform case, so this is a title convention rather than config.
iMicknl
added
the
code-quality
iMicknl
added a commit
that referenced
this pull request
Jun 21, 2026
## Problem The `autolabeler` rules added in #2143 were never actually executed. The main `release-drafter/release-drafter` action only **drafts releases** — it parses the full config (hence the deprecation warnings in its logs) but does **not** apply labels. Labeling is a *separate* sub-action: `release-drafter/release-drafter/autolabeler`. Consequences observed: - #2145 was opened with **no labels** at all. - #2143 (`code-quality`) and #2144 (`ci`) were labeled **manually**, not by the action. - No "add label" activity appears in any release-drafter run log. Since the changelog draft groups by label, an unlabeled merged PR falls into the uncategorized bucket — the exact drop we set out to fix. ## Fix - Add a dedicated `autolabel` job (PRs only) using the `release-drafter/release-drafter/autolabeler` sub-action, with `pull-requests: write`. - Gate the existing `update_release_draft` job to `push` events, so each job only runs where it applies (no wasted draft run per PR). - Pin both to the same SHA (v7.4.0). Follow-up to #2143 / #2144. ## Verification After merge I'll confirm a new PR gets labeled by `github-actions` (not manually). Also worth a separate cleanup: relabel #2144 `ci` -> `code-quality`, and deprecate the stale `ci` label (not part of the new scheme).
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
1 participant
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.
Why
Now that #2144 strips the Conventional-Commit prefix, the summary becomes the first word the reader sees in the changelog. Conventional Commits' default lowercase summary renders as:
Capitalizing the summary gives the expected:
Why a convention, not config
Release Drafter
replacerscan find/replace text but cannot transform case (no callback / uppercase function), so forcing the capital via regex isn't possible. The only route is writing the title capitalized:feat: Add X.Documents this in AGENTS.md. Follow-up to #2143 / #2144.