6 ms·
There are workarounds to get git to search harder or to commit things in a way that's helpful for large-scale file-shuffles, but to be honest I've rarely found
by ryanianian 6y ago
There are workarounds to get git to search harder or to commit things in a way that's helpful for large-scale file-shuffles, but to be honest I've rarely found this to be enough of a reason to not move things around. The end result is a much more productive and purposeful place for code to live and grow. This said, moving files and moving code within those files at the same time is a recipe for confusing yourself and git. Move files first, then content.
- deleted 6y ago[deleted]
- nitrogen 6y agoA few options to look at specifically: --follow, -M, and -C. Less related to refactoring I also find --first-parent and --merges useful