I’m seeing some really weird behavior when subscribing to the push: tags event:
on: push: tags: - '*'
When a build is initiated from the creation of tag, a step doing git fetch --prune --unshallow --tags does not fetch the tag that initiated the build. This build was initiated from creating tag 1.0.3 as can be seen by the refs/tags/1.0.3 value of github.ref. But as the output from git fetch shows, tag 1.0.3 isn’t fetched:
From https://github.com/SwedbankPay/kramdown-plantuml * [new branch] develop -> origin/develop * [new branch] master -> origin/master * [new tag] 1.0.0 -> 1.0.0 * [new tag] 1.0.1 -> 1.0.1 * [new tag] 1.0.2 -> 1.0.2
Not having access to the tag makes GitVersion not work properly, generating the version number 1.1.0-tags-1-0-3.1+15 instead of 1.0.3.
Can someone please explain why the tag that initiated the build is not available to the build itself?
PS: I sincerely hate the forum software you’ve chosen here and the fact that something so specifically targeted at developers makes it impossible to use Markdown or HTML to format messages. I enjoy writing GitHub issues 178 times more than writing into this godforsaken “rich text” field. Please, burn this to the ground. Thank you.