Repository navigation
(MINOR) Generate release notes from commit messages - #6
Merged
Merged
Conversation
GitHub's generated release notes only link a PR when its merge commit hash matches, which misses PRs in many cases. Build the notes from the commit messages since the previous tag with mikepenz/release-changelog-builder-action instead, and link any #123 reference to its PR or issue. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PaulTrampert
added a commit
to PaulTrampert/PTrampert.SimplePatch
that referenced
this pull request
Oct 4, 2026
…flow (#146) Closes #145 ## Cause Breaking changes for 2.0 are staged on `release/2.0`, but `dotnet-library.yml` only triggered `pull_request` runs for `main`, so #139–#142 had no CI build. ## Fix - Add `release/**` to the `pull_request` branches. Publishing still runs only for `main`: the `push` trigger is unchanged, and the shared workflow publishes only when `github.ref` is `main`. - Document the release-branch flow in `AGENTS.md`. PRs into `release/<major>` are squash-merged. The release PR into `main` is rebase-merged, because release notes are now built from commit subjects (PaulTrampert/github-workflows#6), and a squash would collapse them to one line. A `pull_request` run uses the workflow file from the base branch, so `release/2.0` needs this commit too. It has nothing `main` lacks, so it can be fast-forwarded to `main` once this merges. ## Rejected alternatives - Shipping releases by pushing `release/2.0:main` directly, with a merge-gate check and an admin bypass. That kept commit SHAs for GitHub's generated release notes, which notes built from commit subjects no longer need. ## Outside this PR Already applied through the API: rebase merging enabled for the repository, `rebase` allowed in both `main` rulesets, and a new `release/**` ruleset (squash only, build and PR-title checks required). ## Tests No code changes. YAML change verified by inspection; this PR's own build exercises the `main` trigger. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <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
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.
Summary
generate_release_notes: trueonsoftprops/action-gh-releasewith notes built bymikepenz/release-changelog-builder-actioninCOMMITmode. The notes list each commit summary since the previous tag, newest first.#123references into links to<repo>/issues/123, and GitHub redirects that URL to/pull/123when the number is a PR. References that are already linked ([#9](...)) and cross-repo references (owner/repo#10) are left alone.git describe(the same approach ascheck-changes), and runs the action inofflineModeso it reads commits from local git without making API calls.artifacts/so the release file globs can't pick up anything from the checkout.Testing
I ran the action (v6.4.0) locally in a
node:24container against a test repo, using the same configuration:Closes #7 and refs #8→Closes [#7](…/issues/7) and refs [#8](…/issues/8)(PATCH) Fix a thing (#12)→(PATCH) Fix a thing ([#12](…/issues/12))[#9](x)andother/repo#10were left unchangedThis has not been run in a real release yet.
🤖 Generated with Claude Code