如何更新GIT流释放分支名称以反映次要版本的增加？
假设我开始使用以下方式发布：
git流量释放1.5.0
然后，我作为Bitbucket管道的CI/CD的一部分发布了发行分支，以构建用于测试团队的版本：
git流发布1.5.0
然后，我对此分支上的错误进行了修复，但尚未提交。我觉得该版本一定是1.5.1。不一定，但是即使在内部，也很高兴知道1.5.0中发现的错误已在1.5.1中关闭。
如何使用git流将版本更新为1.5.1？ （我知道如何使用普通的git命令创建分支，但我正在尝试使用git流技术）。还是我试图以错误的方式使用git流？
Lets say I started release using:
git flow release start 1.5.0
Then I published the release branch as part of CI/CD for bitbucket pipelines to build this release for testing team:
git flow release publish 1.5.0
Then I made a fix to a bug on this branch, but have not committed it yet. I feel like the version must be something like 1.5.1. Not necessarily, but even internally it would be nice to know that bug found in 1.5.0 have been closed in 1.5.1.
How do I update version to 1.5.1 using git flow? (I know how to create branches using plain git commands, but I am trying to use git flow technique). Or am I trying to use git flow the wrong way?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
分支名称实际上并不重要，因此您不必更改它。将发行分支合并到
Master（或main）是表示生产部署的原因，并且在同一中有多个构建（通常是标记）释放分支。旁注：在我的公司中，我们最近停止了使用git流的存储库，我们最近停止了编号的发行分支，现在我们有一个长期的释放分支。 （它只是在发行版之间暂时处于休眠状态。）这样的主要原因是，我们不必每次创建新的分支名称时都必须在分支上设置安全性。
侧面注释：根据我的经验，git流量命令不足以保证使用它们（或至少专门使用它们）。我更喜欢所有团队成员学习普通的git命令，我们尝试清楚地记录下来。尤其是因为我们的许多开发人员还使用其他分支策略的存储库。
The branch name doesn't actually matter, so you don't have to change it. Merging the release branch into
master(ormain) is what signifies a deployment to production, and it doesn't matter if you have multiple builds (typically tagged) on the same release branch.Side Note: at my company in a repo that uses Git Flow we recently stopped making numbered release branches and now we have one long lived release branch. (It simply goes dormant temporarily between releases.) The main reason for this was so we didn't have to setup security on the branch every time we created a new branch name.
Side Side Note: in my experience, the Git Flow commands aren't useful enough to warrant using them (or at least using them exclusively). I'd prefer all team members learn the normal Git commands, and we try to document them clearly. This is especially because many of our developers also use other repos that are on different branching strategies.