我正在探索将GitVersion用于许多项目。 git flow模型似乎对客户端非常有吸引力，因为它们还没有自动化测试，但是需要更好地了解release / *分支的稳定性。
在纯GitFlow中，似乎允许提交发布/v1.x.x，但是我不确定我是否喜欢。相反，我想指定从发布分支中获取的bugfix / another-fix-for-v1.xx分支，然后PR到基本发布分支中，然后挑选（使用Azure DevOps Cherry-pick功能）回到主线开发分支。
使用以下配置，我无法从发布分支release / v1.1.0（gv：v1.1.0-rc）中获取要计算的 bugfix / another-fix-for-v1.xx 版本。 .X + Y）。我希望增加：继承优先。
assembly-versioning-scheme: None
branches:
develop:
regex: dev(elop)?(ment)?$
mode: ContinuousDeployment
tag: beta
increment: Minor
prevent-increment-of-merged-branch-version: false
track-merge-target: true
tracks-release-branches: true
is-release-branch: false
master:
regex: master
mode: ContinuousDelivery
tag: ''
increment: Patch
prevent-increment-of-merged-branch-version: true
track-merge-target: false
tracks-release-branches: false
is-release-branch: false
release:
regex: ^release?[/]
mode: ContinuousDelivery
tag: rc
increment: Patch
prevent-increment-of-merged-branch-version: true
track-merge-target: false
tracks-release-branches: false
is-release-branch: true
feature:
regex: ^feature?[/]
mode: ContinuousDelivery
tag: alpha
increment: Inherit
prevent-increment-of-merged-branch-version: false
track-merge-target: false
tracks-release-branches: false
is-release-branch: false
bugfix:
regex: ^bugfix?[/]
source-branches: ['release/', 'development']
mode: ContinuousDelivery
tag: alpha
increment: Inherit
prevent-increment-of-merged-branch-version: true
tracks-release-branches: true
pull-request:
regex: (pull|pull\-requests|pr)[/-]
mode: ContinuousDeployment
tag: PullRequest
increment: Inherit
prevent-increment-of-merged-branch-version: false
tag-number-pattern: '[/-](?<number>\d+)[-/]'
track-merge-target: false
tracks-release-branches: false
is-release-branch: false
hotfix:
regex: ^hotfix(es)?[/]
mode: ContinuousDelivery
tag: beta
increment: Patch
prevent-increment-of-merged-branch-version: false
track-merge-target: false
tracks-release-branches: false
is-release-branch: false