New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tag always ends up on the main-branch #824
Comments
Facing the same issue. |
wordrak
added a commit
to lanalabs/release-drafter
that referenced
this issue
Jul 21, 2021
Use commitish from action inputs. Fixes release-drafter#824.
HI, any news related to the commitish input param? Any way to work-around this issue? |
jetersen
pushed a commit
that referenced
this issue
Sep 6, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
first of all, thanks for this great workflow.
I develop on the "main" branch. On a release, I create a branch "rel" and bump the version (in a version.json), thereby creating a new commit). "rel" is now one commit ahead of "main".
I override the "tag" and the "commitish" parameter of the workflow. Commitish seems to successfully pickup "rel" as the branch to work on. Yet, the tag always ends up on "main".
My workflow is here. The latest run is this. Note that I have forcefully pushed the 8.4.0-tag to be on the right commit.
Thanks a lot.
The text was updated successfully, but these errors were encountered: