ci: enforce conventional commits and add release engineering - #4
Merged
Merged
Conversation
Nothing on this account was versioned: 0 tags, 0 releases, 0 changelogs. That left no way to say which build is running or what changed between two points. - scripts/check-conventional-commits.sh validates every commit on a pull request. The changelog is generated from those subjects, so a commit that does not parse silently disappears from the release notes. - scripts/build-release-notes.sh groups commits since the previous tag into Markdown - .github/workflows/commits.yml enforces the format on every PR - .github/workflows/release.yml publishes a GitHub Release on a v* tag - add CHANGELOG.md Co-Authored-By: Claude Opus 5 (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
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.
Point 4 of the estate review: 0 tags, 0 releases, 0 changelogs anywhere on the account.
Conventional commits are now validated on every PR (the changelog is generated from them), release notes are built from those commits, and pushing a
v*tag publishes a GitHub Release.