What is the best practice of committing the changes back to Git

salaros's Avatar


24 Dec, 2017 06:19 PM

Recently I started to actively use AppVeyor for my open-source .NET projects
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

git commit --amend && git push --tags --force

however the commands above will trigger another tagged build and so on (ending up in a loop situation).
I'm quite sure that people have already thought of an elegant way to accomplish what I'm trying to archive.

  1. Support Staff 1 Posted by Ilya Finkelshte... on 24 Dec, 2017 11:00 PM

    Ilya Finkelshteyn's Avatar

    Set Do not build tags if you use UI or skip_tags: true if you use YAML.

    Also though you probably already know all this, but maybe you can find this useful: https://www.appveyor.com/docs/how-to/git-push/

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

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


? 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