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
Release CI workflow is tagging main even when releasing from a different branch/commit.
The build happens on the desired branch correctly, but a tag is then pushed on main and the release linked to that tag.
Details
It seems softprops/action-gh-release@v1 should be updated to v2 and that we should provide it with target_commitish if we wish to push a tag on a different branch.
Fix would be to:
set target_commitish to the branch the workflow is being run on if it is not set
add optional target_commitish input to workflow to allow tagging a specific commit
Update the rest of the workflow to use the passed target commit if set, to create the build based on that instead of latest commit.
The text was updated successfully, but these errors were encountered:
Bug Report
Summary
Release CI workflow is tagging main even when releasing from a different branch/commit.
The build happens on the desired branch correctly, but a tag is then pushed on main and the release linked to that tag.
Details
It seems
softprops/action-gh-release@v1
should be updated to v2 and that we should provide it withtarget_commitish
if we wish to push a tag on a different branch.Fix would be to:
target_commitish
to the branch the workflow is being run on if it is not settarget_commitish
input to workflow to allow tagging a specific commitThe text was updated successfully, but these errors were encountered: