support skipping linting

with the transition from validate-commit-msg to commitlint, one missing feature that i notice is the ability specify that a commit should skip linting by including a keyword in the message. i initially asked if this would be added in the thread about the transition, but was righty directed here to open an issue.

in the case of validate-commit-msg, the keyword was simply starting the commit message with WIP, which has worked well for us when a commit is a step toward one of the categories, but does not complete the effort.

would it be possible to support similar functionality in commitlint to save us from needing to configure some sort of wrapper in all of our projects?

[byCedric]

@marionebl Sure, I will create one in my lunch break! Approximately in 1 or 2 hours. Thanks for responding this quickly.

[marionebl]

TL;DR

• Git has the fixup! and squash! semantics
• commitlint uses said semantics to determine ignored commits
• I prefer sticking to git semantics to keep things simple
• Let’s discuss use cases that do not fit fixup! and squash! semantics
• If we add this it should be configurable

The long story

commitlint currently skips commits according to git semantics - meaning that merge, fixup and squash commits are ignored automatically. The relevant test cases can be found here.

If i understand your use case for this correctly prefixing the WIP commits with fixup! instead could be the idiomatic way to ignore commits. E.g.:

• WIP: This is something I id =>fixup! This is something I did
• WIP: Some more work =>squash! Some more work

What are your thoughts on this?

Beginning commit messages with WIP feels different to me as git itself does not attach additional semantics to it. If we add this functionality I’d tend to go with some regex option matching commits that should be ignored, e.g.

module.exports = {
  rules: {},
  ignore: /(^WIP:|\[skip-lint\]$)/
};