Hey! are you committing tangled changes?
Hey! are you committing tangled changes?
复制标题
DOI：
10.1145/2597008.2597798
复制
发表时间：
2014-06
期刊：
影响因子：
--
通讯作者：
Hiroyuki Kirinuki;Yoshiki Higo;Keisuke Hotta;S. Kusumoto
中科院分区：
文献类型：
--
作者：
Hiroyuki Kirinuki;Yoshiki Higo;Keisuke Hotta;S. Kusumoto
虽然有一条原则指出提交应该只包括对单个任务的更改，但开发人员并不总是遵守这一原则。这意味着代码存储库经常包含包含纠结更改的提交。这种复杂变化的存在阻碍了对代码存储库的分析，因为大多数挖掘软件存储库（MSR）方法的设计假设是，每次提交只包括单个任务的更改。在本文中，我们提出了一种技术来告知开发人员他们正处于提交复杂变更的过程中。建议的技术利用过去提交中包含的更改来判断给定的提交是否包含纠缠的更改。如果它确定提议的提交可能包括纠结的更改，它就如何将纠结的更改拆分为一组未纠结的更改提供建议。
Although there is a principle that states a commit should only include changes for a single task, it is not always respected by developers. This means that code repositories often include commits that contain tangled changes. The presence of such tangled changes hinders analyzing code repositories because most mining software repository (MSR) approaches are designed with the assumption that every commit includes only changes for a single task. In this paper, we propose a technique to inform developers that they are in the process of committing tangled changes. The proposed technique utilizes the changes included in the past commits to judge whether a given commit includes tangled changes. If it determines that the proposed commit may include tangled changes, it offers suggestions on how the tangled changes can be split into a set of untangled changes.