Difference between revisions of "Nice Version Control"
Jump to navigation
Jump to search
(actual content) |
m (good commit messages) |
||
Line 5: | Line 5: | ||
always diff before you commit, to avoid committing anything unintentionally | always diff before you commit, to avoid committing anything unintentionally | ||
+ | |||
+ | write accurate, meaningful and ideally concise commit messages. | ||
commit smaller, logically grouped changes together- this makes it easier to | commit smaller, logically grouped changes together- this makes it easier to |
Revision as of 15:19, 26 September 2005
very basic and generic guidelines for working with others using a revision control system:
update your working copy before modifying anything
always diff before you commit, to avoid committing anything unintentionally
write accurate, meaningful and ideally concise commit messages.
commit smaller, logically grouped changes together- this makes it easier to revert a specific change without reverting unrelated stuff, too.
avoid conflicts when possible by knowing who's working on what parts
when implementing major changes, check in with others working on the project
try to implement major changes in a branch first
keep branches in sync, to make it easier to merge back into mainline