-
-
Notifications
You must be signed in to change notification settings - Fork 4
fix: ensure that branches are sorted #18
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
Conversation
|
@rickstaa I think this is ready for review (then release). Thank-you for this github/action! |
|
This regression is likely due to
Workaround is to set the following before the checkout action. |
…d unzipping artifacts before release
Oh my god, thank you so much! This is exactly what fixed it for me. ❤️ |
|
My CI/CD pipeline was failing because of this upgrade of git. I was unable to deploy tags in production. Thanks a lot for the quick workaround! As mentioned, the git config command must me done before the first checkout. To make it clear for those stumbling on this issue, the workaround looks like this: steps:
# Step added as a workaround for https://github.com/rickstaa/action-contains-tag/pull/18
# TODO: bump version of action-contains-tag and remove this workaround step after PR above is merged
- name: Workaround regression action-contains-tag due to git update
run: git config --global remote.origin.followRemoteHEAD never
- name: Checkout
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Check if tag refers to a commit in main branch
uses: rickstaa/action-contains-tag@v1
with:
reference: 'main'
tag: ".... tag you want to check....." |
## Summary Copies the fix referenced in rickstaa/action-contains-tag#18 and implemented in pybwa https://github.com/fulcrumgenomics/pybwa/blob/9193fb98fdebf63ed264fa08667b4dbbf79c796c/.github/workflows/publish_pybwa.yml#L16-L22
|
@rickstaa bump |
…d unzipping artifacts before release
…d unzipping artifacts before release
…d unzipping artifacts before release
|
@rickstaa sorry to bother you, any chance you can look at this? |
|
Closing as no response from maintainer. |
In some cases I have seen:
[action-contains-tag] Branch 'remotes/origin/HEAD -> origin/main' does not contain tag '1.4.2'.We see that the branch is incorrect (it should be
main). See log from my repo below, as well as this PRs own action (first and second commit here)example log