Closed fearnlj01 closed 1 year ago
Since it's just dailies (no stable release) then I just deleted the existing 2.0.1.40
and 2.0.1.41
and made it recreate 2.0.1.40
.
(I also accidentally closed the wrong issue with my commit, but we don't talk about that.)
Looking at the list of tags for Shokofin, commit
bef066d
has ended up being tagged twice with both2.0.1.40
&2.0.1.41
.Running
git for-each-ref --sort=-creatordate --count 1 --format="%(refname:short)" "refs/tags/"
(as per theWyriHaximus/github-action-get-previous-tag@v1
action) currently outputs2.0.1.40
however, which leads to the next attempt at setting a tag to be the already existing2.0.1.41
...I'd imagine the easiest resolution would be to manually create tags for
2.0.1.42
&2.0.1.43
(or just delete the tag for2.0.1.40
) Don't think I can PR anything like this sadly!I can however, as below, include the git commands to create the tags we'd expect if everything played nice at the expected commits however!