Splitting Commits via Past Code Changes
Splitting Commits via Past Code Changes
复制标题
通过过去的代码更改拆分提交
DOI：
--
复制
发表时间：
2016
期刊：
影响因子：
--
通讯作者：
S. Kusumoto
中科院分区：
文献类型：
--
作者：
Hiroyuki Kirinuki;Yoshiki Higo;Keisuke Hotta;S. Kusumoto
通常说我们不应在单个提交中执行代码更改形式任务。这样的代码更改称为Tangledons。进行纠结的变化对开发人员有害。例如，合并一部分纠结变化与其他企业的一部分是昂贵的。此外，这种纠结的存在更改了Hindersanalyzing代码存储库。这是因为大多数MiningSoftware存储库方法都是在假设订单下设计的，仅包括一个任务的更改。在本文中，Wepropose的一种技术，该技术告诉开发人员他们即将纠缠的变化。该技术还建议如何通过使用过去的代码更改将agiven提交分为多个提交。该技术使开发人员能够确定他们是否接受建议或提交的作用。通过提供此类支持的助长者，他们可以避免进行纠结的变化。
It is generally said that we should not perform code changes formultiple tasks in a single commit. Such code changes are called tangledones. Committing tangled changes is harmful to developers. Forexample, it is costly to merge a part of tangled changes with othercommits. Moreover, the presence of such tangled changes hindersanalyzing code repositories. That is because most of the miningsoftware repository approaches are designed under the assumption thatevery commit includes only changes for a single task. In this paper, wepropose a technique which informs developers that they are about tocommit tangled changes. The technique also suggests how to split agiven commit into multiple commits by using past code changes. Theproposed technique allows developers to determine whether they acceptthe suggestion or commit as it stands. By providing such support todevelopers, they can avoid committing tangled changes.