diff --git a/.github/skills/bump-version/SKILL.md b/.github/skills/bump-version/SKILL.md index d166dcf0e..b1c82292e 100644 --- a/.github/skills/bump-version/SKILL.md +++ b/.github/skills/bump-version/SKILL.md @@ -52,7 +52,7 @@ Use `v` only when comparing or creating Git tags. git --no-pager log --reverse --format='%s%x09%H' "${previous_tag}..HEAD" ``` -7. Build the PR release notes by grouping all commits into user-facing buckets. +7. Build the PR release notes by grouping all commits into user-facing buckets and attributing every supporting PR to its contributor. 8. Commit the version bump with an imperative message: ```text @@ -80,13 +80,15 @@ Use these buckets, omitting empty buckets: Prefer concise, user-facing summaries over raw commit subjects. Combine related commits into one bullet when they describe the same release-note item. -For each bullet, include the supporting PR title and number in parentheses: +For each bullet, include the supporting PR title, number, and contributor handle in parentheses. Put the contributor immediately after the PR reference: ```text -- summary sentence (PR title #number). +- summary sentence (PR title #number by @contributor). ``` -Do not include commit SHAs in the PR release notes. If a commit subject already contains a PR number, use it. Otherwise, use `gh` to inspect the commit or associated PR when possible. +Use the PR author's GitHub login as the contributor, not the commit author or a co-author. When one bullet combines multiple PRs, repeat `#number by @contributor` for each supporting PR. + +Do not include commit SHAs in the PR release notes. If a commit subject already contains a PR number, use it, then use `gh` to retrieve the PR title and `author.login`. Otherwise, use `gh` to inspect the commit or associated PR when possible. ## PR body template @@ -101,19 +103,19 @@ Previous release tag: `` Features: -- ( #). +- ( # by @). Fixes: -- ( #). +- ( # by @). Docs: -- ( #). +- ( # by @). Maintenance: -- ( #). +- ( # by @). ## Validation @@ -127,16 +129,16 @@ Remove empty buckets before opening or updating the PR. ```markdown Features: -- parser comment policy strips template/style comments while preserving legal comments, with CLI, Node, docs, and benchmark coverage (feat: strip template and style comments in parser and support legal comments #326). -- CSS module delivery now emits import-map data URI modules and the commerce demo defaults to module styles (Emit style modules via importmap + dataURI instead of