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
hi @jackton1,
i see you fixed this. so the the current_branch is also detected if the wf is triggered by a tag.
one more question:
i experienced that my workaround works only if the tag is set on the latest/head-commit. if you tag an older commit the branch still can not be detected.
will this be an issue for you too?
@arauchbergerIt would be helpful if you can include an example application which explains the issue you are seeing.. No, I don’t think it should be an issue.
Is this feature missing in the latest version?
Is your feature request related to a problem? Please describe.
when the workflow is triggered by a created/pushed tag it's hard to find the branch-name the tag is created on.
Describe the solution you'd like?
i suggest the following approach via
git log ...
(works at least for me):Describe alternatives you've considered?
No response
Anything else?
i'm not good in opening/handling PR's on foreign GitHub-projects, that's why i just write this suggestion to still contribute 'a little bit'.
i like your gh-action!
thanks
Code of Conduct
The text was updated successfully, but these errors were encountered: