improve feature flag handling

[tessus]

While the update-informer is a nice idea and works great, I am running a build process every day and distribute the binary on all my VMs and machines. Thus I do not need it, but unfortunately I haven't found a config option to disable the check. But even with such an option, I'd first have to actually use a config file in the standard location. Thus when using git-cliff in a repo with a cliff.toml or on a machine without a config file, it would still check for version updates.

I checked the build instructions and it mentions the available feature flags.

Unfortunately it is not up-to-date and this got me thinking:

It is not possible to remove an item from the list of default features (e.g. --no-features update-informer - argh what a bummer, the cargo folks still haven't made this available) and adding all other features seems fragile, since - as we can see - the documentation is missing one (gitea).

I certainly do not want to remove it from the default features, since in most cases it makes perfect sense and it might break people's build workflows. I am just wondering what the best option would be.

I think first of all the documentation should be updated and I will create a PR for that.
Additionally I'd like to add another meta feature (integrations, all-integrations, or whatever):

integrations = ["github", "gitlab", "gitea", "bitbucket"]

What do you think @orhun? Does this make sense or is it just a wacky idea?

[orhun]

Hey!

I certainly do not want to remove it from the default features, since in most cases it makes perfect sense and it might break people's build workflows. I am just wondering what the best option would be.

Not sure if there is anything actionable there... It's simply how cargo works 🤷🏼‍♂️
I'm okay with how the feature flags work right now.

Additionally I'd like to add another meta feature (integrations, all-integrations, or whatever):

Good idea, however I think it already exists and called remote. integrations is a better name for sure though, maybe we can also add that.

Definitely send a PR for docs updates. Good catch!

[tessus]

Good idea, however I think it already exists and called remote. integrations is a better name for sure though, maybe we can also add that.

The remote festure is used by the integrations.

I can create a PR what I had in mind, it's probably easier that way. It takes just one click to close it. ;-)

Definitely send a PR for docs updates.

will do