tag:help.appveyor.com,2012-11-13:/discussions/problems/3918-git-tags-appear-both-as-new-tags-and-new-branches-limiting-deploy-restriction-optionsAppVeyor: Discussion 2018-10-19T08:17:41Ztag:help.appveyor.com,2012-11-13:Comment/388133362016-01-01T21:00:48Z2016-01-01T21:00:49ZGit tags appear both as new tags and new branches, limiting deploy restriction options<div><p>See for example this build:</p>
<p><a href="https://ci.appveyor.com/project/hymerman/foo-bestversion/build/1.0.18">
https://ci.appveyor.com/project/hymerman/foo-bestversion/build/1.0.18</a></p>
<p>I pushed a new tag, '1.0.3'. AppVeyor shows this as both a new
tag, and a new branch. There is no branch called '1.0.3'. Since I
have deployment restricted to new tags on the 'master' branch, the
log shows that the branch doesn't match and it doesn't run the
deploy step.</p>
<p>Am I doing something wrong? I think I understand the AppVeyor
side correctly; even the AppVeyor docs on deployment use new tags
on master branch as their example:</p>
<pre>
<code>- provider: Environment
name: production
on:
branch: master
appveyor_repo_tag: true</code>
</pre></div>Ben Hymerstag:help.appveyor.com,2012-11-13:Comment/388133362016-01-02T01:13:32Z2016-01-02T01:13:32ZGit tags appear both as new tags and new branches, limiting deploy restriction options<div><p>If branch has the same name as tag then webhook payload didn't
have the information about base branch. You can check webhook
"Recent deliveries" on GitHub to see that.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/388133362016-01-03T22:44:50Z2016-01-03T22:44:50ZGit tags appear both as new tags and new branches, limiting deploy restriction options<div><p>Brilliant, thanks - I've looked at the data on GitHub's end and
you're<br>
right. In this case I pushed the tag before the commit, which may
have<br>
confused things, even though I later deleted then force pushed a
new tag<br>
with the same name to try to do it the right way round. I'll try
pushing<br>
the commit then the tags next time, sounds like that should work
as<br>
expected.</p></div>Ben Hymers