tag:help.appveyor.com,2012-11-13:/discussions/problems/16523-appveyor-is-creating-tags-with-the-same-name-of-the-branches-after-releaseAppVeyor: Discussion 2018-11-12T21:00:44Ztag:help.appveyor.com,2012-11-13:Comment/460388412018-09-07T06:16:17Z2018-09-07T06:16:17ZAppVeyor is creating tags with the same name of the branches after release<div><p>You can set <code>tag:</code> key in GitHub <code>deploy:</code> section of yaml configuration file. See <a href="https://www.appveyor.com/docs/deployment/github/#provider-settings">here</a> for more available settings.</p>
<p>Also, if you don't want the second tag created you can add <code>skip_tags: true</code> to the top level of your config file as outlined in the <strong>note</strong> section <a href="https://www.appveyor.com/docs/deployment/github/#promoting-selected-tag-to-github-release">here</a>.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/460388412018-09-11T21:40:40Z2018-09-11T21:40:40ZAppVeyor is creating tags with the same name of the branches after release<div><p>Ty Owen, is it possible to not push tags ? It appears that is a default thing in appveyor to push tags for each build, or am I wrong ?</p></div>patrickelectrictag:help.appveyor.com,2012-11-13:Comment/460388412018-09-12T00:23:04Z2018-09-12T00:23:04ZAppVeyor is creating tags with the same name of the branches after release<div><p>From <a href="https://help.github.com/articles/about-releases/">GitHub</a></p>
<blockquote>
<p>At their core, Releases are based on Git tags.</p>
</blockquote>
<p>In other words, any GitHub release will create a tag.</p></div>Owen McDonnell