333. Adds text about naming bugfix branches

This commit is contained in:
Will Kahn-Greene 2011-07-24 15:19:38 -04:00
parent e60f8719dd
commit 0a80ad41a9

View File

@ -63,6 +63,10 @@ Further, if you isolate your changes to a branch, then you can work on
multiple issues at the same time and they don't conflict with one multiple issues at the same time and they don't conflict with one
another. another.
Name your branches using the isue number and something that makes it clear
what it's about. For example, if you were working on tagging, you
might name your branch ``360_tagging``.
Properly document your changes Properly document your changes
------------------------------ ------------------------------