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 Nov 14, 2023. It is now read-only.
I found that the task always tags on the latest commit, and not on the commit specified in the build version.
For example, I create a build for commit hash 12345 (the first commit), and create another build for commit 67890 (the second and latest commit), if I choose to release the build with commit 12345, it will tag the branch at the second and latest commit (i.e. 67890), not on the first commit, which is associated with the build used in the release.
Another scenario: I create a build for commit 12345, and then hold-off creating a release. Another commit comes in (67890). If I create a release for the build with commit 12345, the commit with hash 67890 gets tagged, even if a build is not created for it.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I found that the task always tags on the latest commit, and not on the commit specified in the build version.
For example, I create a build for commit hash
12345
(the first commit), and create another build for commit67890
(the second and latest commit), if I choose to release the build with commit12345
, it will tag the branch at the second and latest commit (i.e.67890
), not on the first commit, which is associated with the build used in the release.Another scenario: I create a build for commit
12345
, and then hold-off creating a release. Another commit comes in (67890
). If I create a release for the build with commit12345
, the commit with hash67890
gets tagged, even if a build is not created for it.The text was updated successfully, but these errors were encountered: