feat: generate changelog from scratch

[Conaclos]

Hi there!

Why

I encountered a problem in the genration of my changelog for several versions of a project. See this issue for more details.

What

I would like to generate from scratch my changelog and then have proper entries for each version.

[weaintplastic]

I've just used conventional-changelog-cli to do the job for me.

conventional-changelog -p angular -i CHANGELOG.md -s -r 0

This will generate the changelog for all your previouse tags.

[Conaclos]

@weaintplastic Thanks for the suggestion :)

[stevemao]

standard-version --first-release doesn't work for you?

[weaintplastic]

@stevemao unfortunately not. --first-release is not going through the entire commit history and creates a changelog from scratch. It just does not bump the version number.

[bcoe]

@weaintplastic @Conaclos I'll lead with my periodic apology related to disappearing from open-source😛

One thought, perhaps we could document some advanced topics, e.g., using conventional-changelog to regenerate commits, in docs/advanced.md?

[stevemao]

I feel like this feature should live here too by adding another flag...

[weaintplastic]

@stevemao I agree. Would be really helpful to integrate that.

[philpoore]

+1

[ronanjia]

+1

[ekil1100]

+1

[r15ch13]

Simply adding resetChangelog: true to the context would make this possible.

const context = { version: newVersion, resetChangelog: true }

See: https://github.com/conventional-changelog/standard-version/blob/106d0390f7fe73c93131511caef17f2dca37fd6a/lib/lifecycles/changelog.js#L38-L46

Would be simple to implement with a command flag. Example: https://github.com/r15ch13/standard-version/commit/8561f1ca880b4eb000a614ae9dbc6f5fcaab2d60

[D-Nice]

^ would be quite a useful feature.

[snebjorn]

Any progress on this?

[luizfelipelaviola]

I need this too... Multiple years and nothing...

[escapedcat]

conventional-changelog -p angular -i CHANGELOG.md -s -r 0

This works:

npx conventional-changelog-cli -p angular -i CHANGELOG-foo.md -s -r 0

See comment further above

[stevenKirill]

I have the opposite problem. When I run npm run release, I got a new tag, but all previous commits included. How can I separate commits, so it doesn't include commits from previous release , and just include new commits ?