We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some projects adapt change types to fit their needs (e.g using present tense Fixes instead of Fixed or adding an Improved change type).
My suggestion for a possible quick solution would be having a .kacl file in $HOME containing a list of change types such as:
.kacl
$HOME
Adds Changes Breaking Changes Improves Fixes Deprecates Removes
This file -- if present -- would be read by kacl and overwrite the default change types during lint checks.
kacl
I believe this would be a nice feature to have as it provides a good degree of flexibility.
Keep up the awesome work!
The text was updated successfully, but these errors were encountered:
Good idea! This project uses https://github.com/oscarotero/keep-a-changelog/ for handling the parsing and manipulating of changelogs, so we'd need to add support for this in there. Currently it's hardcoded here: https://github.com/oscarotero/keep-a-changelog/blob/master/src/Release.js#L17 , but that might be possible to change pretty easily.
Sorry, something went wrong.
and now keep-a-changelog project enables users to add custom types 😺
keep-a-changelog
No branches or pull requests
Some projects adapt change types to fit their needs (e.g using present tense Fixes instead of Fixed or adding an Improved change type).
My suggestion for a possible quick solution would be having a
.kacl
file in$HOME
containing a list of change types such as:This file -- if present -- would be read by
kacl
and overwrite the default change types during lint checks.I believe this would be a nice feature to have as it provides a good degree of flexibility.
Keep up the awesome work!
The text was updated successfully, but these errors were encountered: