Thread with 5 posts
jump to expanded post
github CI debugging makes me want to tear my hair out at the best of times but we just hit something that makes me feel fucking insane
how the fuck can git describe --always fail to see the new tag, it literally says in the log from the checkout that it's there, what the fuck, what the fuck, what the fuck
I wonder if it's doing something cursed in the checkout that means the tag is there but the annotation on it somehow isn't?
fuck it, let's see if not using actions/checkout and doing a manual git clone works better
this bit might be the culprit?
git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules origin +765d0c16207d6ed5dcc3d2b1d78778f39fb89ea4:refs/tags/v0.420.69
since it's pinning a hash to the tag, it might effectively skip the annotation somehow?
manual git clone fixed the issue yay
@hikari This has also confused me in the past... `git fetch --tags --force` or for even less fetching `git fetch --force origin tags/<tag>:tags/<tag>` also work to replace the lightweight tag the action creates with the actual annotated tag.