ci(quality gate): add commitlint to the workflow #4
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds commitlint workflow and release automation to enforce conventional commits and automate package versioning, changelog generation, and npm publishing. The implementation introduces a quality gate for commit messages on PRs and a manual release workflow triggered from the main branch.
Changes:
- Added commitlint configuration and CLI dependency for commit message validation
- Added GitHub Actions workflows for commitlint validation and release automation using release-please
- Configured release-please with manifest and config files for version management
- Added Husky commit-msg hook for local commit validation
Reviewed changes
Copilot reviewed 7 out of 8 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/commitlint.yml |
New workflow to validate commit messages on PRs using commitlint |
.github/workflows/release.yml |
New manual workflow for version bumping, building, and publishing to npm |
.github/workflows/analyse.yml |
Updated stage comments for consistency |
.husky/commit-msg |
Added husky hook to run commitlint locally on commits |
.release-please-config.json |
Configuration for release-please with package metadata |
.release-please-manifest.json |
Manifest file tracking current version for release-please |
package.json |
Added @commitlint/cli as dev dependency |
pnpm-lock.yaml |
Lockfile updates for new commitlint dependencies |
Files not reviewed (1)
- pnpm-lock.yaml: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
.github/workflows/release.yml
Outdated
| with: | ||
| tag_name: ${{ needs.bump.outputs.tag_name }} | ||
| generate_release_notes: true | ||
| body_path: CHANGELOG.md |
There was a problem hiding this comment.
The body_path: CHANGELOG.md references the entire changelog file. Since release-please generates release-specific content, consider using the release body from release-please outputs instead, or ensure this points to a release-specific changelog section. The entire changelog file might be too verbose for a single release.
There was a problem hiding this comment.
@copilot open a new pull request to apply changes based on this feedback
|
@bnachtweh I've opened a new pull request, #5, to work on those changes. Once the pull request is ready, I'll request review from you. |
|
@bnachtweh I've opened a new pull request, #6, to work on those changes. Once the pull request is ready, I'll request review from you. |
Co-authored-by: bnachtweh <32386227+bnachtweh@users.noreply.github.com>
Add a workflow that can be manually triggered from main branch. The flow does the following: