3 ms·
Oh hell no, Visual Studio has this behaviour by default (commit all changes if nothing staged) and what we end up with is that some people keep checking in vari
by whizzter 6y ago
Oh hell no, Visual Studio has this behaviour by default (commit all changes if nothing staged) and what we end up with is that some people keep checking in various experiments and privately modified launch config files (that should not be in the repo anyhow but that's another story related to the tools) that end up causing a lot of unnecessary merge conflicts when you pull in their changes (where you were really only expecting some other part).
- nicoburns 6y agoWe deal with this via code review. Anything with such files is going to get instantly rejected. And people soon learn not to do it.
- tremon 6y agoSo with every new hire, you have burden the reviewer again? Wouldn't it be better to make the default so that Visual Studio burdens the primary developer, instead of the reviewer?
- kubanczyk 6y agoWe prefer to automate everything that's automatable, and then a bit more, because reviewing is hard work.