You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be working as intended, but does not seem to be desirable behavior to me.
With a release regex of regex: ^release-:
If I clone my repo, am on a branch that tracks-release-branches (develop below), and do not have my release branches local then the wrong version is reported until/unless I either I pull the latest release branch local or change my regex.
I can work around it with a regex of regex: release-
but this feels wrong, as then release is valid anywhere in the branch name.
I am currently using this as my workaround, which is acceptable regex: ^(origin/)?release-
and I can understand why this might be needed from a regex perspective, but it does not feel logical to me that it is from a usage perspective.
Is this workaround the correct fix, should this be fixed in the code, or am I missing something else?
Thanks!
Indeed, the fact that a branch exists only under the remote origin should be invisible to the user. GitVersion should treat origin branches as if they were local.
This may be working as intended, but does not seem to be desirable behavior to me.
With a
release
regex ofregex: ^release-
:If I clone my repo, am on a branch that tracks-release-branches (
develop
below), and do not have my release branches local then the wrong version is reported until/unless I either I pull the latest release branch local or change my regex.I can work around it with a regex of
regex: release-
but this feels wrong, as then release is valid anywhere in the branch name.
I am currently using this as my workaround, which is acceptable
regex: ^(origin/)?release-
and I can understand why this might be needed from a regex perspective, but it does not feel logical to me that it is from a usage perspective.
Is this workaround the correct fix, should this be fixed in the code, or am I missing something else?
Thanks!
GitVersion.yml
:The text was updated successfully, but these errors were encountered: