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
In addition to #31 I'd like to have a tool for Cutting a Release in the sense of:
processing commits since last git (annotated?) tag pointing to a release, so we can determine if such a subset of commits imply a patch, minor or major release number and calculate it (based on commitizen as pointed out in Generate changelog entry from pre-defined commit format #31)
based on the same subset of commits, use their information to build a list of CHANGELOG entries to be inserted into the existing (or newly created if missing) CHANGELOG.md file
update mix.exs (and optionally an adjacent VERSION file) accordingly to the new computed version number
commit these changes with a meaningful git commit message
tag that commit with the computed version number
push the commit and tag to the remote origin
I'm aware this is such a broadening of the scope of the project in its actual form, so feel free to discard or amend at will 😄
The text was updated successfully, but these errors were encountered:
In addition to #31 I'd like to have a tool for Cutting a Release in the sense of:
CHANGELOG
entries to be inserted into the existing (or newly created if missing)CHANGELOG.md
filemix.exs
(and optionally an adjacentVERSION
file) accordingly to the new computed version numberI'm aware this is such a broadening of the scope of the project in its actual form, so feel free to discard or amend at will 😄
The text was updated successfully, but these errors were encountered: