A push which updates multiple refs does not show up as a tag build

Hello,
I have a practice of committing and tagging the commit and then doing an atomic push, like git push --atomic origin master my-tag-name-1.0.0. The last time I did this, I noticed that AppVeyor only triggered a single build. This build was not a tag build. I had to delete the tag and re-push the tag to trigger a tag build.
I am using Bitbucket.
Is this a known limitation? Since git allows multiple refs to be updated in a push, I was expecting AppVeyor to support this. I would prefer not to separate the push of the version update with the associated tag.
Thanks.

Reply to this discussion Internal reply only staff will see it

Markdown

Attaching KB article:

»

Attach files

Up to 10MB each.

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac