如何将单个提交归因于多个开发人员? [英] How to attribute a single commit to multiple developers?

查看:102
本文介绍了如何将单个提交归因于多个开发人员?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我熟悉的所有版本控制系统的工作方式是每次提交都归属于单个开发人员。敏捷工程的兴起,特别是结对编程,已经导致了两个开发人员为同样的任务作出重大贡献的情况,例如一个错误修复。



归因问题在工作环境中不会太大,因为项目经理会意识到配对正在进行的工作,但如果两个开源贡献者决定配对并推出一些代码,那么该怎么办?到一个不知道他们在一起工作的特定项目。有没有办法像Git这样的版本控制系统将特定的补丁分配给多个开发人员?解决方案

解决方案

一种解决方案是设置一对名字:

  git config user.nameChris Wilson and John Smith

以下是一个与其他临时解决方案相关的错误报告:

Bug git-core:Git应该支持多个作者进行提交


The way all version control systems I'm familiar with work is that each commit is attributed to a single developer. The rise of Agile Engineering, and specifically pair programming, has lead to a situation where two developers have made a significant contribution to the same task, a bug fix for example.

The issue of attribution won't be too much of a big deal in a work environment since the project manager will be aware of the work the pairs are doing, but what about if two open source contributors decide to pair up and push out some code to a particular project that has no idea they're working together. Is there any way for a version control system like Git to attribute a particular patch to multiple developers?

解决方案

One solution would be to set a name for the pair:

git config user.name "Chris Wilson and John Smith"

Here is a related bug report with other temporary solutions:

Bug git-core: Git should support multiple authors for a commit

这篇关于如何将单个提交归因于多个开发人员?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆