tag:help.appveyor.com,2012-11-13:/discussions/questions/15804-what-is-the-best-practice-of-committing-the-changes-back-to-gitAppVeyor: Discussion 2018-08-25T02:26:01Ztag:help.appveyor.com,2012-11-13:Comment/443747972017-12-24T18:19:03Z2017-12-24T18:19:04ZWhat is the best practice of committing the changes back to Git<div><p>Recently I started to actively use AppVeyor for my open-source .NET projects<br>
AssemblyInfo and .NET Core version package are really cool features, however I would like to commit these changes back upon tagged builds. I can create a script which adds write privileges for GitHub repo + use something like</p>
<p>git commit --amend && git push --tags --force</p>
<p>however the commands above will trigger another tagged build and so on (ending up in a loop situation).<br>
I'm quite sure that people have already thought of an elegant way to accomplish what I'm trying to archive.</p></div>salarostag:help.appveyor.com,2012-11-13:Comment/443747972017-12-24T23:00:02Z2017-12-24T23:00:02ZWhat is the best practice of committing the changes back to Git<div><p>Set <code>Do not build tags</code> if you use UI or <code>skip_tags: true</code> if you use YAML.</p>
<p>Also though you probably already know all this, but maybe you can find this useful: <a href="https://www.appveyor.com/docs/how-to/git-push/">https://www.appveyor.com/docs/how-to/git-push/</a></p></div>Ilya Finkelshteyn