4 ms·
I use Scrum and I usually commit about once an hour. More if I'm just bug-fixing or correcting typos or adding comments. Committing every 30 seconds seems like
by MalcolmDiggs 11y ago
I use Scrum and I usually commit about once an hour. More if I'm just bug-fixing or correcting typos or adding comments.
Committing every 30 seconds seems like it would knock me out of my flow so often that I wouldn't get anything done.
That being said, if I'm working in the same files as someone else, I'll commit every few minutes (and so will they) so that the amount of conflicts we're creating don't get out of hand.
- obfuscatedgeek 11y agoCurious, if Scrum makes you get into this mindset that you have to commit every hour ?
- MalcolmDiggs 11y agoMaybe, but I think it's more of a continuous-delivery thing than a scrum thing. I just commit after I add anything meaningful to the codebase (to get it out to users as quickly as possible), and that usually ends up being once an hour.
- GFK_of_xmaspast 11y agoYou could imagine some sort of IDE plugin that commits-and-pushes with automatic messages on every save, but god help you if your CI triggers on every push and your test suite is non-trivial.
- MalcolmDiggs 11y agoHaha, yeah that would be way too much CI. We use CodeShip for CI/CD and they let you add "--skip-ci" to the commit message to skip deployment for trivial stuff.