Asbjørn Ulsberg

I'm not sure, but I think the problem may be that the tag `1.7.1` is applied to the `support/1.7` branch and not to `main`. I don't think `support` branches are...

You can [configure `source-branches`](https://gitversion.net/docs/reference/configuration#source-branches) as a sort of opposite relationship to "merge target".

Hm, good question, @HHobeck. I'm not using that feature myself, did not implement it, and am not sure exactly how it's supposed to work. It may be that we didn't...

> The release candidate 1.0.0 has not been merged and tagged on master. But it will be properly merged to develop and deleted. Why would a `release/*` branch be merged...

> I'm also thinking about it in which circumstances the MergeMessageVersionStrategy is used in the gitflow worflow. Cannot find any scenario. Maybe it is good for the github workflow with...

> Okay and why is the TrackMergeTarget property be true per default in the develop branch configuration? (Please see ConfigurationBuilder.cs) I don't see how `MergeMessageVersionStrategy` is related to `TrackMergeTarget`?

> I think it is quite common to merge from release to develop and not to master (at least not at the same time). Think about it if you finalize...

> What do you mean with the changelogs, version number increments, etc.? I cannot see any problems with that. A merge from release to develop is just a normal commit:...

I think @orionstudt is right. We should probably clarify this in the documentation.

There is no progress on this since I don't use either AzDO nor dynamic repositories myself. I would recommend that you do a clone of the repository instead of using...