{subsection: Making the branch}
+{subsubsection: Starting from an existing public branch}
+
{code}
# Lets decide on the name "V7_1-GreatFeature-branch". This means we
# are going to branch from the end of V7_1-branch, so you should make
@@ -53,6 +55,32 @@
$ git branch -f V7_1-GreatFeature-branch origin/V7_1-GreatFeature-branch
{endcode}
+{subsubsection: Starting from a private (local) branch}
+
+If you have a local/private branch, you can push it up to the master. If you didn't follow the naming conventions above, you'll need to rename it, which is what the following documents. This example assumes a local branch named "bname", made off of V7_6-branch.
+
+{code}
+# Make sure we're on the right branch
+$ git checkout bname
+
+# Rename it to match the name guidelines.
+$ git branch -m V7_6-bname-branch
+
+# First, get it into the main repository
+$ git push origin V7_6-bname-branch
+
+# now rename the local copy to an old version just in case you need it
+$ git branch -m V7_6_bname-branch-old
+
+# Checkout bname from the origin and track it.
+$ git checkout -b bname origin/V7_6-bname-branch
+
+# Now you can delete the bname-old when you are satisfied bname is in the
+# repository and it is happy.
+# git branch -D V7_6-bname-branch-old
+{endcode}
+
+
{subsection: Document the branch name}
You must add a description of the new branch at GitBranchDescriptions. The description should include the name of the person who created or is responsible for the branch, the date, where the new branch came from, what it is for, and any plans for when/where it's going to be merged back into (if we know them).
