This page permanently redirects to gemini://d.moonfire.us/blog/2021/07/27/commitlint-gitlab-ci/.
=> Up a Level
I have a slowly evolving set of practices when it comes to writing processes. One of the first ones is setting up a Git repository. This always starts with configuring husky[1], semantic-release[2], conventional-commits[3], and commitlint[4]. (I'm working on updating my Yeoman generator[5] to make this a lot easier, but that will be later this week.)
=> 1: https://typicode.github.io/husky/#/ | 2: https://semantic-release.gitbook.io/semantic-release/ | 3: https://www.conventionalcommits.org/en/ | 4: https://commitlint.js.org/#/ | 5: https://www.npmjs.com/package/generator-mfgames-writing
Sadly, my Git host of choice, Gitlab[6], has a little problem with commitlint. It blows up on the first few commits which lead to me reporting this[7] issue.
=> 6: https://gitlab.com/ | 7: https://github.com/conventional-changelog/commitlint/issues/885
Since I'm usually creating a number of new Git repositories in a month and commitlint is one of the first things I set up, I ended up writing a little NPM utility[8] to handle the bug for me since the original package (rightfully, I feel) don't want to add Gitlab-specific code:
=> 8: https://www.npmjs.com/package/commitlint-gitlab-ci
npx commitlint-gitlab-ci -x @commitlint/config-conventional
It seems to work fairly well for me, I've been messing with it for a little while and haven't had too many complaints.
Categories:
=> Programming
Tags:
=> commitlint | commitlint-gitlab-ci | Conventional Commits | Gitlab | Husky | semantic-release
Below are various useful links within this site and to related sites (not all have been converted over to Gemini).
=> Now | Contact | Biography | Bibliography | Support
=> Fiction | Fedran | Coding | The Moonfires
=> Categories | Tags
=> Privacy | Colophon | License
=> Mailing List
=> https://d.moonfire.us/blog/2021/07/27/commitlint-gitlab-ci/ This content has been proxied by September (ba2dc).Proxy Information
text/gemini;lang=en-US