arturcic on 5.3.6
x.0... afaik the runtime can execute any of the other minor-compiled executables.
C:\Users\appveyor\.nuget\packages\gitversiontask\5.1.3\build\GitVersionTask.targets(10,9): error : FileLoadException: Could not load file or assembly 'Newtonsoft.Json, Version=18.104.22.168, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'. Could not find or load a specific file. (0x80131621)
Easiest probably to use .NET Core global tool
dotnet tool install --global GitVersion.Tool --version 5.1.3
Hiho. I just adopted gitversiontask into a project where I also use github actions to build the project. Running the build on github actions however fails and as far as I grasp, gitversiontask deletes files in the .git/ directory which in turn causes the git repository to become corrupt.
Thoughts? Ideas? Am I doing something wrong?
/home/runner/.nuget/packages/gitversiontask/5.1.3/build/GitVersionTask.targets(10,9): warning : 2020-01-16 19:19:16 WARN [01/16/20 19:19:16:29] Unable to read cache file /home/runner/work/event-sorcery/event-sorcery/.git/gitversion_cache/61BA4200E58C0052BC7002D1FE8C8D7E6C5D701C.yml, deleting it.
Hello there. I'm looking at the examples for GitFlow and at the same time reading the description for Git Branching Strategies for GitFlow. What I cant wrap around my head is the example for Minor Release Branches when combined with the description.
When the branch for release/1.3.0 is created, I figure that the version on branch develop is bumped to 1.4.0 (minor+1) by looking at the version given in the release branch name. A commit is done on the develop branch yielding
1.4.0-alpha.1 (1 = number of commits ahead of release/1.3.0), so far so good. Now to my confusion... Once the release is completed and release/1.3.0 is merged with master and develop I do not understand how the version for develop is determined as
1.4.0-alpha.4? How can develop be 4 commits in front of master at this point since all commits done in release/1.4.0 have been merged both to develop and master?