4 ms·
There are plenty of smaller changes that are just way easier with a single commit. A small API call with just two or three consumers, a documentation change, et
by argonaut 5y ago
There are plenty of smaller changes that are just way easier with a single commit. A small API call with just two or three consumers, a documentation change, etc. The multistage approach is certainly good for big changes.
- stkdump 5y agoAlso, if you do all changes at once, you can also run the whole testsuite and find problems quicker. Sure, you could still later split the work up into many commits. But even when problems come up that you didn't see in the tests, it is easier to revert the work if it indeed is a single commit. The real reason why I still sometimes prefer many small commits is to reduce the chance of merge conflicts.
- kohlerm 5y agoYou can do automatic bisecting https://git-scm.com/docs/git-bisect https://git-scm.com/docs/git-bisect which you cannot easily do with multiple repos