Skip to content

Commit

Permalink
Iterating on "Contributing" README
Browse files Browse the repository at this point in the history
  • Loading branch information
DaleMcGrew committed Feb 13, 2016
1 parent 969db61 commit 5deed1a
Showing 1 changed file with 12 additions and 12 deletions.
24 changes: 12 additions & 12 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,23 +19,23 @@ Instead of direct check-ins to this repository, we use pull requests. Here is an
“WebApp” does not conflict with the cloned folder from https://github.com/wevote/WebApp
3. Add the repository you forked as the upstream repository
* To keep your fork synced with wevote/WebApp, use these the command line commands:
```
```
cd /Users/<Your Home Directory>/<Your Projects Folder>/PersonalGitForks/WebApp
git remote add upstream git@github.com:wevote/WebApp.git
```
```
* Confirm with "git remote -v"
```
$ git remote -v
origin https://github.com/DaleMcGrew/WebApp.git (fetch)
origin https://github.com/DaleMcGrew/WebApp.git (push)
upstream git@github.com:wevote/WebApp.git (fetch)
upstream git@github.com:wevote/WebApp.git (push)
```
```
$ git remote -v
origin https://github.com/DaleMcGrew/WebApp.git (fetch)
origin https://github.com/DaleMcGrew/WebApp.git (push)
upstream git@github.com:wevote/WebApp.git (fetch)
upstream git@github.com:wevote/WebApp.git (push)
```
* For detailed instructions, see: [Step 3: Configure Git to sync your fork](https://help.github.com/articles/fork-a-repo/)
4. To keep your personal fork synchronized with wevote/WebApp
```
git fetch upstream
```
```
git fetch upstream
```
* Once you do this, you can `git remote -a` to see what repositories you have available to you.
* For detailed instructions, see: [Syncing a fork](https://help.github.com/articles/syncing-a-fork/)
* If you get an error like "Permission denied (publickey)" see: [Error permission denied public key](https://help.github.com/articles/error-permission-denied-publickey/)
Expand Down

0 comments on commit 5deed1a

Please sign in to comment.