What is the best practice of committing the changes back to Git
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.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | 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
1 Posted by Ilya Finkelshte... on 24 Dec, 2017 11:00 PM
Set
Do not build tagsif you use UI orskip_tags: trueif 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/
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:25 AM.