Splitting Commits via Past Code Changes

@article{Kirinuki2016SplittingCV,
  title={Splitting Commits via Past Code Changes},
  author={Hiroyuki Kirinuki and Yoshiki Higo and Keisuke Hotta and Shinji Kusumoto},
  journal={2016 23rd Asia-Pacific Software Engineering Conference (APSEC)},
  year={2016},
  pages={129-136}
}
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… CONTINUE READING