Hello,

Thanks for a great product

I am using git flow at the moment.

When I finish a release, git flow merges the local release branch into master, and develop, and tags the commit.

In App Veyor this operation results in 3 builds being queued up - I have attached a screenshot showing the builds.

The issues is, I only want 2 builds to be queued when this happens - the commit to develop triggers a build, and the tagged commit on master should trigger a build of master..however It seems the commit on master is queued twice to appveyor - because it has a tag. This causes me a problem because I publish a nuget package when master is built. So at the moment, the first build (which is triggered by the tag) runs successfully and nuget package gets published. Then the other build runs (same commit) and that one fails because the nuget package can't be published a second time.

This means that often the appveyor build status badge on my README.md file shows as failed, as the last build is failing due to this problem.

So my question - is there anything I can do to get around this issue, and prevent these duplicate builds? If possible i'd be able to tell AppVeyor not to build tags perhaps?

Many thanks

Darrell