Load config-conventional in absence of user configuration

[marionebl]

In the lieu of a "zero configuration" movement in the wider JS tooling community we should evaluate if the inital obligatory configuration step for commitlint could be omitted.

Expected Behavior

• Load @commitlint/config-conventional if no user configuration was found
• Do not merge user configuration onto @commitlint/config-conventional if found

Current Behavior

• No configuration is loaded if no user configuration is provided
• Running commitlint without configuration lets every commit message pass

Considerations

• Should be considered a breaking change, consumers might depend on the "pass through" behaviour of unconfigured commitlint

[marionebl]

Could be made obsolete

• cli: Provide an init command #48
• docs: explain minimal sensible config better #107

[escapedcat]

I think this can be closed in favour of #48 . And as you pointed out with #107 commitlints now throws an error on missing config.

[byCedric]

Yes, I'd also like this, especially when we are using the GitHub Actions. I tested a bare-minimum setup for actions, and well, with this change we can actually use it on every type of repository. I mean for GoLang, Ruby or other projects this could be great!

[byCedric]

I've got a couple of edge cases here I think. What should happen if...

1. ... the user doesn't provide any configuration (not through CLI or config/package files).
2. ... the user only provides rules/formatters/flags in configuration.
3. ... the user only provides rules/formatters/flags in cli.

I think case 1 is fairly simple, it should load conventional config. But cases 2 and 3 might be a bit harder. The way I see it, the conventional should only load for option 1 and 3. When the user specifies a configuration, it should not change that by any means. But might be that some users expect this anyway. But that could be fixed by good documentation of course.

[byCedric]

Ok, got something working for @commitlint/load. Just to check on some assumptions I made.

1. Is it ok to load it in this package? I mean, that's the place where we can differentiate "no config provided at all" as opposed to "no extends found, add conventional" (in @commitlint/cli.

2. When I load @commitlint/config-conventional in @commitlint/load it throws an error that it could not find this package. Even after I add this as a dependency of the load package. I guess my only plausible solution for this is creating an absolute/relative path to the nested conventional package in node_modules, or am I missing something else?