chore: add conventional commit linting #160
Merged
Conversation
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
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
barakmich
previously approved these changes
Nov 25, 2025
tstirrat15
force-pushed
the
add-conventional-commit-linting
branch
from
b4321f4 to
6a7ea1f
Compare
tstirrat15
force-pushed
the
add-conventional-commit-linting
branch
from
6a7ea1f to
76556fc
Compare
barakmich
approved these changes
Dec 2, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Part of preparing this repo for the use of
release-please. We need to have conventional commits in place, so this adds a linter for that and does some other drive-by refactors to workflows.Changes
create-pull-requestaction tag with a conventional commit (featto trigger a release)Testing
Review. See that tests pass.