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
The uplift changelog --all command is designed to generate a complete changelog based on the current history of the repository. This is incredibly useful if migrating an existing repository to use Uplift. However, its current design doesn't quite work, as it will only generate a CHANGELOG.md:
If there is no existing file. This requires a deletion that ultimately prevents the command from executing due to a dirty repository state
It generates a commit which may not include a version number and can produce a confusing git history
This command should be treated as a utility function that updates the existing CHANGELOG.md in situ and requires the user to handle the modified file manually
Steps to reproduce it
Clone an existing repository with a CHANGELOG.md file and run uplift changelog --all
Your uplift configuration
No response
Which version?
v2.17.0
Which operating system(s) are you using?
All
Optional debug output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
What happened?
The
uplift changelog --all
command is designed to generate a complete changelog based on the current history of the repository. This is incredibly useful if migrating an existing repository to use Uplift. However, its current design doesn't quite work, as it will only generate aCHANGELOG.md
:This command should be treated as a utility function that updates the existing
CHANGELOG.md
in situ and requires the user to handle the modified file manuallySteps to reproduce it
CHANGELOG.md
file and runuplift changelog --all
Your uplift configuration
No response
Which version?
v2.17.0
Which operating system(s) are you using?
All
Optional debug output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: