On Thu, Sep 8, 2011 at 12:42 PM, Clive Crous <clive.cr...@gmail.com> wrote:
> The company I work for sent out an email this morning instructing us
> to, from now on, commit all source code changes for whatever we're
> currently working on and push (to central
> company git repository), regardless of the progress, status or state
> every half-an-hour so that they see the
> changes being made and can monitor productivity. Thoughts on this?
A commit should be a logical set of changes for one particular alteration.
Since these 30-minute auto-commits would most likely be work-in-progress
commits, they shouldn't, in my opinion, be pushed. I can think of a few
reasons: things are easier for every other person who might have to read the
commits (imaging having to read _at least_ 6 separate commits for a change
that happened to take 3 hours; reverting, say, a feature is simpler; and you
have the chance to neaten up a commit before its seen. Not only that, but if
you have a lot of automatic commits, how many of those would, say, break a
build or automated tests?
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at