From 7dc5e4d0b354ea87f662ef51a870d00f3cc33dd7 Mon Sep 17 00:00:00 2001
From: Thomas Rushby <t.w.rushby@soton.ac.uk>
Date: Tue, 9 Jun 2020 15:51:55 +0100
Subject: [PATCH] Amend order of 'how' bullet list

---
 gitBranches.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gitBranches.md b/gitBranches.md
index 9e67014..5afd14a 100644
--- a/gitBranches.md
+++ b/gitBranches.md
@@ -13,9 +13,9 @@ For this reason branches should be small small things that fix or make a specifi
 We have found the best workflow is to 
 
  * [fork](https://happygitwithr.com/fork-and-clone.html) the original repo to your personal githib/gitlab account. This means you do not need to be a member of the original repo to work on it. It also helps to prevent accidents to the original master.
- * add the original master as an [upstream remote](https://happygitwithr.com/upstream-changes.html)
  * create a new RStudio project using _your fork_ of the repo
    * It's possible you may need to set up a [new ssh key on github](https://happygitwithr.com/ssh-keys.html) to do this. What does this do? It tells github that the device you are using is authenticated. Tip: give the new SSH key on github a helpful name - e.g. the device it is associated with!
+ * add the original master as an [upstream remote](https://happygitwithr.com/upstream-changes.html)
  * **make a new branch in _your fork_ of the orginal repo**. Do some work, commit it locally.
  * when it works push your branch back up to the *original* repo
  * open a new pull request to merge your branch into the master
-- 
GitLab