Hm, maybe it is better to simply disable commit message validation on master? 🤔

✅ Build karma 2926 completed (commit c076f6b558 by @chrisbottin)

✅ Build karma 529 completed (commit c076f6b558 by @chrisbottin)

✅ Build karma 528 completed (commit c076f6b558 by @chrisbottin)

Hm, maybe it is better to simply disable commit message validation on master? 🤔

@devoto13 yes we could do that but do you mean permanently? If we are happy with having no commitlint running on master then we can just disable it (I can submit another PR) ... otherwise we do need this PR to have different header-max-length rules.

Let me know

Yes, permanently. If you think about it, the check is not really actionable: one can't revert or fix the commit in master branch. So we can only run it in PRs/branches where we can prevent a bad commit message. But it's just my opinion. It's up to @johnjbarton to decide which approach to use.

Yes @devoto13 is right, I like the no-master solution better. @chrisbottin can you do it?

✅ Build karma 535 completed (commit 138b283a52 by @chrisbottin)

✅ Build karma 2932 completed (commit 138b283a52 by @chrisbottin)

✅ Build karma 534 completed (commit 138b283a52 by @chrisbottin)

✅ Build karma 2933 completed (commit 339ac71f89 by @chrisbottin)

✅ Build karma 536 completed (commit 339ac71f89 by @chrisbottin)

✅ Build karma 535 completed (commit 339ac71f89 by @chrisbottin)

@johnjbarton done as requested.

🎉 This PR is included in version 6.1.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀