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
{{ message }}
This repository has been archived by the owner on May 16, 2021. It is now read-only.
Thanks, I appreciate the feature suggestion. I agree that it is unfortunate that Chandler overwrites existing releases without warning; I've created a separate issue for that: #28.
In terms of the actual titles, I am happy with the current behavior, which is to use the version number only. This matches the style of projects I maintain and use. However I understand that this is not a universal practice, as I see there are some popular GitHub repositories that follow different conventions.
I'll leave this issue open for consideration in case I have time to revisit Chandler's design in the future.
⚠️This project is no longer actively maintained. I have found myself embracing tools like release-drafter to keep release notes updated automatically, rather than relying on a manually edited CHANGELOG.md. If you are interested in taking over chandler development, let me know by opening an issue.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
currently the github "tag title" is filled with just "version"
however, i used to fill there also release date:
https://github.com/eventum/scm/releases/tag/v3.1.2
2016-09-06, Version 3.1.2
now
chandler
will overwrite that with3.1.2
once ranperhaps set the tag title as the line present in changelog file itself:
but care should be taken with the
[]
-s (stripped because the link itself is not included): #27The text was updated successfully, but these errors were encountered: