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
I'm a very happy user of GitPunch. In my own projects I use a release tag naming convention release/$version. In the email received today I noted that a link is broken. It seems that the release/ part was skipped. The link in the email I've got was: https://github.com/szpak/mockito-java8/releases/tag/2.4.0
As the release process (including tagging) is done automatically (there are no manual changes in tags), the easiest explanation is that GitPunch removes the release/ as a part of the Git path (to the latest occurrence of /).
The text was updated successfully, but these errors were encountered:
I'm a very happy user of GitPunch. In my own projects I use a release tag naming convention
release/$version
. In the email received today I noted that a link is broken. It seems that therelease/
part was skipped. The link in the email I've got was:https://github.com/szpak/mockito-java8/releases/tag/2.4.0
instead of:
https://github.com/szpak/mockito-java8/releases/tag/release%2F2.4.0
As the release process (including tagging) is done automatically (there are no manual changes in tags), the easiest explanation is that GitPunch removes the
release/
as a part of the Git path (to the latest occurrence of/
).The text was updated successfully, but these errors were encountered: