Remove no description and general scope

[mascardoso]

Hi, I have a couple of questions which from my POV are rather a nice to have for decreasing cognitive load when reading a changelog.

• Every time I do a release with an empty description I see the sentence *No description* within the changelog. Why? Would it be possible to hide it as it adds zero value?
• Is it possible to hide the scope general? Maybe we just don't want anything. Meaning when I commit something like git commit -m 'feat: add feature 1' I would just like to see something:

FEATURES
    - add feature 1
    - add feature 2

Thank you so much

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template!

[BobAnkh]

Hi, @mascardoso

Thank you for your questions. For the first question, I think this can be repalced with empty content. So if you mean like that:

## v1.1.1

*No desctription*

### Feature

to be replaced with

## v1.1.1

### Feature

I think we can have this in the next release when I'm free. And if you have time, you can make a pull request on this feature.

For the second question, I think it is hard to directly add thoses commit message. I'm afraid this might make the format wierd for the changelong. I have thought to hide those commits. But see #11 and #75. You can use other words or characters to replace general.

If you have better ideas on the second question, please discuss with me.

[BobAnkh]

@mascardoso
One of the problem should be solved in the new release v1.2.1.