> IMO there's almost never a good reason to have automated commit This depends entirely on the quality of dev tools available. Also, commit =/= shipped code:

> IMO there's almost never a good reason to have automated commit This depends entirely on the quality of dev tools available. Also, commit =/= shipped code: you may have a automated commits and keep a human in the loop before shipping, by way of rejectable Pull-Request (or the proprietary equivalent). A simple library upgrade will result in a wave of commits/bot-authored PRs 1. Human makes a change to a core library, changing it from v1 to v2 2. Bot identifies all call-sites and refactors to v2-equivalent, creating 50 PRs for 50 different teams. One change, 51 commits.