When pushing tags and some tags are rejected, GitHub actions don't seem to trigger on tags that did get pushed. Is this intended?

[flyx]

Select Topic Area

Question

Body

A colleague of mine just tried to tag a release which should trigger an action. He did

git push --tags

and got something like:

 * [new tag]         v1.2.7 -> v1.2.7
 ! [rejected]        v1.0.7 -> v1.0.7 (already exists)
error: failed to push some refs to 'github.com:corp/repo.git'

The GitHub action for the push of v1.2.7 did not trigger. It is specified to trigger on

on:
  push:
    tags:
      - "v*"

There is no run of the action recorded in the Actions tab. It simply never ran.

We deleted the tag and he pushed again with git push origin v1.2.7. That did trigger the action.

I assume the action originally did not trigger because of the error he got. But why should the action on v1.2.7 depend on whether another tag was pushed? Is this intended behavior?