Is there a configuration template for validating against the conventionalcommits.org spec?
See original GitHub issueI just came across gitlint via searching for a golang implementation of https://conventional-changelog.github.io/commitlint/#/, which validates against the https://www.conventionalcommits.org/en/v1.0.0-beta.3/ spec.
It looks like gitlint is pretty configurable; I was wondering whether anyone had created a .gitlint
config that made it validate against the CC spec? If not - would one be welcome?
(I’d prefer to use a golang based tool, personally, since the environment is simpler to deploy and maintain for engineers - copy a binary, run it, vs maintain a node and npm setup.)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Conventional Commits
The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an...
Read more >What about work in progress commits · Issue #38 - GitHub
examle: i'm work on feature and dont know my code is correct or no, but i must go home. i will push a...
Read more >Setup and Customize Conventional Commits and Semantic ...
CommitLint validates commits to see if matches the standard formatting of a conventional commit. In this example, I'm going to use Commitizen ......
Read more >A specification for structured commit messages | Hacker News
On come on, this entire "spec" can be summarized in two sentences. It can be validated with a 13 character regex.
Read more >ramsey/conventional-commits - Packagist
ramsey/conventional-commits is a PHP library for creating and validating commit messages according to the Conventional Commits specification. It also ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Added ‘revert’ keyword in e95fe6122fae5930534f46dfc15dcd3bb7cf8059
Gitlint 0.12.0 with support for this will be released over the next few days. Closing this issue.
I’ve been using this to enforce conventional commits:
.gitlint
gitlint-rules.py
Then just run
gitlint
and it should get picked up. What do you think? Would something like this be worth adding as an optional (default off) title rule? Having to put this in a separate file in each repo is kind of a pain, so getting it officially added to gitlint or supporting plugins viapip install ...
would be better!