功能分支和代码元数据丢失

发布于 2024-11-05 21:04:25 字数 306 浏览 3 评论 0原文

我们广泛使用功能分支作为开发策略。简而言之,我们要做的就是始终保持稳定的主干,而开发人员在可能损坏的分支上实现复杂的功能,直到该功能经过充分的测试。那时,分支被合并回主干,然后在主干上进行完整的集成/回归测试周期等。

我遇到的问题如下:在分支中实现所述功能的过程中,显然存在大量提交到分支。每个提交都有具有潜在教育和文档(?)价值的评论,有时可能非常有用。当您将分支大规模合并回主干时,所有这些注释都会丢失,并替换为无用的“将废话合并到主干”类型的注释。

有人有任何可以帮助保存元数据的解决方案吗?在您看来这也是一个问题吗?

PS我使用的是SVN。

We use feature branching extensively as a strategy for development. In short and somewhat simplistic terms, what that allows us to do is to keep a stable trunk at all times while developers implementing complex features work on a potentially broken branch until the feature has been tested adequately. At that point the branch is merged back into trunk followed by a full integration/regression testing cycle on the trunk etc.

The problem I have is as follows: During the course of implementing said feature in the branch, there are obviously a host of commits made to the branch. Each commit has comments that hold potential educational and documentational(?) value that can sometimes be very useful. When you do a mass-scale merge of the branch back into trunk all of these comments get lost and replaced with a useless "Merging blah into trunk" type comment.

Does anyone have any solutions that can help preserve that metadata? Is this even a problem in your opinion?

P.S. I'm using SVN.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文