-
-
Notifications
You must be signed in to change notification settings - Fork 301
Added conventional commits with JIRA scope. #158
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
Conversation
...cope Allows for better enforcement of JIRA issue-driven projects.
Codecov Report
@@ Coverage Diff @@ ## master #158 +/- ## ========================================== - Coverage 91.54% 87.36% -4.19% ========================================== Files 33 35 +2 Lines 769 831 +62 ========================================== + Hits 704 726 +22 - Misses 65 105 +40
Continue to review full report at Codecov.
|
I don't know if this needs to be part of the library, looks more like a plugin, they can easily be created with commitizen_cz_template.
We can create here a new page with a list of alternative commit rules.
What do you think @Lee-W ?
@woile I agree with you. It seems to me we should include only the most used templates in commitizen itself to make it lightweight. Maybe we can create a awesome-commitizen-template list for it?
I'd link directly in the commitizen docs, like "Third party commitizen" or "Packages", or Catalog.
"Third party commitizen" seems to be a better one for me.
@Crystalix007 Thanks for your contribution! As discussed with @woile, we're not planning on making it a part of commitizen. Thus, I'm closing this PR. But we're happy to add this template as a third-party commitizen in our documentation. Please let us know if you want us to add it.
Yes, that's fine, you can create a PR for the docs, create a new section: Third party commitizen.
This adds a new commit standard which basically enforces the scope of the conventional commit to be in the form
project-issueNumber, in order to comply with JIRA issue tagging.