praxtw
Last Updated: February 25, 2016
·
624
· linuxsable
8cedcf6becd4f1503a970ec8faaaa4ed

Commit Early

Commit early and commit often.

Not only does this keep your teammates informed of what you’re doing, it reduces the chance of conflicts.

Keeping commits small allows easy search by that commit title and easy rollback of those changes if they are later found to be poor.

Say Thanks
Respond

1 Response
Add your response

398
10534 128567884189 828694189 2287781 3877042 n

I would add: commit early, commit often, push rarely. You should take care about synchronizing your code with changes in repo (rebasing onto remote repository). You can always --amend to a commit or rebase entire thing locally, so it's not like you're messing up history.

Commits are extremely cheap and nice to keep your progress saved, pushing is not so cheap as it requires you to produce a quality code for others.

over 1 year ago ·
Filed Under