The "type-empty" rule does not work properly.

[FelixLgr]

When using the type-empty rule the separator : is still required.

Expected Behavior

If the type is empty and the scope, there is no need to specify the : separator.

echo 'Toto' | commitlint #true
echo ': Toto' | commitlint #false

Current Behavior

module.exports = {
    extends: ['@commitlint/config-conventional'],
    rules: {
        'type-empty': [2, 'always'],
    },
}

echo 'Toto' | commitlint #false
echo ': Toto' | commitlint #true

Affected packages

• cli
• core
• prompt
• config-angular

Possible Solution

A solution would be either to add a new rule (separator-empty) or to make the type-empty rule remove the : separator.

Your Environment

Executable	Version
commitlint --version	@commitlint/cli@16.2.1
git --version	git version 2.32.0
node --version	v17.5.0

[escapedcat]

Just some thoughts to this.

You are using the config-conventional config. conventionalcommits is expecting a type. So not sure if this is the right approach to combine these two things (conventionalcommits & turning off something which is a default for conventionalcommits).

If you don't want to use conventionalcommits you might want to use your own config in the first place. Not sure of that will lead to a better result but that's seems to be a "better" way to achieve this.

Further we have tests for type-empty. But it looks like that there's an issue with certain configs (i.e. conventionalcommits).

If you are motivated we're happy for a PR to clean up the current situation.

[FelixLgr]

To be completely honest I plan to use the gitmoji configuration instead of the config-conventional one.

With gitmoji I assume that the type is the emoji that's why I want to disable it.

For the PR it would be my pleasure, I will look at what I can do but testing is not necessarily my forte.

Currently the only method I have is to configure the subject-empty But then it doesn't really make sense.

[escapedcat]

To be completely honest I plan to use the gitmoji configuration instead of the config-conventional one.
With gitmoji I assume that the type is the emoji that's why I want to disable it.

Ah ok, yeah, that makes sense. You have a link to that config?

For the PR it would be my pleasure, I will look at what I can do but testing is not necessarily my forte.

No worries. Happy with whatever you can contribute.

Currently the only method I have is to configure the subject-empty But then it doesn't really make sense.

Yeah. Sounds like a new config instead of using config-conventional and turning off its rules.

Thanks for you feedback!

[FelixLgr]

Ah ok, yeah, that makes sense. You have a link to that config?

https://www.npmjs.com/package/commitlint-config-gitmoji

[escapedcat]

Thanks! You think it would be good to mention it i.e. here?: https://commitlint.js.org/#/reference-community-projects

[FelixLgr]

Thanks! You think it would be good to mention it i.e. here?:

Yeah, I thinks it's a good idea. Maybe ask the creator's approval first ? (@arvinxx)

[FelixLgr]

Hello,
I've been looking around and tried to add tests for type-empty by just putting a subject (no ype) and it seems to work. (Here as you said: tests for type-empty)

I may not have understood everything about how to contribute to the project but you want me to fork the project rather than create a branch right?

[escapedcat]

I may not have understood everything about how to contribute to the project but you want me to fork the project rather than create a branch right?

Yeah, you can't open a branch directly here. Forking, open a branch on your fork and create a PR to this repo is usually how it works. Let me know if you run into problems.