Commits can be tricky, as some code can not be executed (opening pages for example) without a commit, but other code is behaving non-logical when commits are added too often (errors rolling back to the last commit).

For a programmer (and for support employees maybe) it can be helpful to stop the debugger on every commit in the code, so you can trace back these places. There is a command that acts a bit like this, to stop on record changes in the database, adding the same kind of option to stop the debugger specifically on commits can be a life saver at times.

Thanks!