You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to be able to edit the CHANGELOG.md before it is committed as part of the semver process. For instance, I would like to be able to use the current tool to decide what everything should look like, and to write the CHANGELOG.md, but not commit the CHANGELOG.md or tags to the repository. This would allow me to edit the CHANGELOG.md, and correct spelling, or make any other changes. This could then be committed into Git.
Ideally, I could then re-run the command, use the --skipChangeLog flag to not generate the CHANGELOG.md (since it was already generated and subsequently edited) and then the normal tag process would run, and the edited CHANGELOG.md would be in the Git repository before the tag so it was clearly included in the release.
The text was updated successfully, but these errors were encountered:
This is more or less related to #513, I agree we need to be able to edit this file. Maybe we don't need to touch the commit logic as we can commit --amend the changes as a workaround.
That would work, and I do use it right now. The only advantage I see in a flag is that you simply do this as part of the versioning process, without having to go back to do the edit and amend. Maybe a flag to simply generate the CHANGELOG.md only, so that it is just another file, then the versioning process could be done with the current flags to not generate a CHANGELOG.md?
It would be nice to be able to edit the CHANGELOG.md before it is committed as part of the semver process. For instance, I would like to be able to use the current tool to decide what everything should look like, and to write the CHANGELOG.md, but not commit the CHANGELOG.md or tags to the repository. This would allow me to edit the CHANGELOG.md, and correct spelling, or make any other changes. This could then be committed into Git.
Ideally, I could then re-run the command, use the --skipChangeLog flag to not generate the CHANGELOG.md (since it was already generated and subsequently edited) and then the normal tag process would run, and the edited CHANGELOG.md would be in the Git repository before the tag so it was clearly included in the release.
The text was updated successfully, but these errors were encountered: