Assistance needed: How to configure my develop
branch to track merges
#4314
Replies: 1 comment
-
I have already answered this question and gave to you the information that the track-merge-message feature you are expecting is only supported in the Generally we cannot helping out with custom workflows. But if you want you can engage me or other person to help you and build custom workflows. Thank you for your understanding. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
Our workflow I am trying to replicate with GitVersion is summed up as follow:
development
branchrelease/
branchesI have a configuration that works if I tag my rc version on the development branch after a merge.
If I don't tag the release the versions are not calculated correctly from the base version, the merges to development is not taken into account when new branches are made.
I am not sure if that is the correct behaviour or if my configuration is incorrect.
GitVersion.yml
A short summary of the steps
The last
assert_version
fails, GitVersion reports'0.0.1-alpha.3'
When I make the tag at the
# THIS DOES NOT BELONG HERE
mark the version is correct in the branch.PS: I wrote a bash script to simulate the unit tests of this project and can provide that if it will help
Beta Was this translation helpful? Give feedback.
All reactions