Missing optional scopes about git-cliff HOT 3 CLOSED

Sure, that would do fine!

Now, all I need is a new release so I can pull the new version in my build image so I can continue automating things. Sagol! :)

from git-cliff.

Hello! Thanks for submitting this. It's implemented in b5df656.

I thought it'd be best to make this configurable via commit_parsers so that a "default" scope can be used for each group:

commit_parsers = [
    { message = "^feat*", group = "Features", default_scope = "general"},
    { message = "^fix*", group = "Bug Fixes", default_scope = "other"},
    { message = "^doc*", group = "Documentation", default_scope = "unscoped"},
]

default_scope will be used if there's no "conventional scope" (in other words: if it's missing). So when you use the config values from above with the following git history:

* docs(config): support multiple file formats
* docs: some commit message

You get the following:

### Documentation

#### Config

- Document values

#### Unscoped

- Some commit message

I think this meets your requirements 😃

default_scope will be available with the next release but feel free to try it out now and report bugs if any.

from git-cliff.

v0.3.0 is released.

from git-cliff.