-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: Add gitlint and document commit conventions #2623
ci: Add gitlint and document commit conventions #2623
Conversation
petejohanson
commented
Nov 8, 2024
- Add gitlint to pre-commit setup
- Update pre-commit setup for installing commit-hooks
- Add "Commit Conventions" contributing docs
- `feat:` - changes that add a new feature | ||
- `fix:` - changes that fix existing functionality | ||
- `refactor:` - changes that refactor existing functionality without adding any new features | ||
- `feat!:`/`refactor!:`/`fix!` - same as above, but indicate a breaking change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Breaking change" might need elaboration here, e.g. as it relates to #2619. We can at least mention the easy ones for now, like board/shield changes or anything that affects user keymaps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a bit more context here. Thoughts?
- `refactor:` - changes that refactor existing functionality without adding any new features | ||
- `feat!:`/`refactor!:`/`fix!` - same as above, but indicate a breaking change. | ||
- `ci:` - changes to our continuous integration setup with GitHub Actions, usually only for the files in `.github/workflows/`. | ||
- `chore:` - grab bag type for small changes that don't fall into any of the above categories. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do dependency updates for e.g. docs fall into docs
or chore
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC, dependabot uses chore
for this.
- `split` - changes to our split keyboard support | ||
- `studio` - changes to our ZMK Studio code | ||
- `display` - changes to to our display code | ||
- `underglow` - changes to to our RGB underglow support |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want lighting
to cover backlight etc. as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It'd be good to keep them distinct, IMHO, since there's already enough confusion generally about the two. IMHO, we should use backlight
for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a separate entry.
I believe this makes #586 redundant. |
01f0146
to
cef4e68
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, suggested mostly cosmetic improvements.
3978eeb
to
6739e47
Compare
* Add gitlint to pre-commit setup * Update pre-commit setup for installing commit-hooks * Add "Commit Conventions" contributing docs Co-authored-by: Cem Aksoylar <[email protected]>
6739e47
to
915d767
Compare