summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorROUVREAU Vincent <vincent.rouvreau@inria.fr>2020-02-11 14:41:35 +0100
committerROUVREAU Vincent <vincent.rouvreau@inria.fr>2020-02-11 14:41:35 +0100
commitacdd28ebf3103c133c5a985219972bec2c7a3460 (patch)
treee82a3f6d7472bd43f45c00537cacccfaf053e923
parent9a182406ff9a419931d7dc20d900515fda2c0ef0 (diff)
Fix some typos
-rw-r--r--for_dev/how_to_use_github_to_contribute_to_gudhi.md8
1 files changed, 6 insertions, 2 deletions
diff --git a/for_dev/how_to_use_github_to_contribute_to_gudhi.md b/for_dev/how_to_use_github_to_contribute_to_gudhi.md
index b9a7f8f7..1ca40386 100644
--- a/for_dev/how_to_use_github_to_contribute_to_gudhi.md
+++ b/for_dev/how_to_use_github_to_contribute_to_gudhi.md
@@ -35,10 +35,14 @@ because you want to see the real gudhi, not just your clone.
## Optional remotes
Optional, if you are interested in one of the old branches
+```bash
git remote add oldies https://github.com/GUDHI/branches.git
+```
Or if you want to spy on someone's work. I assume the someone's account is called **SOMEONE**
+```bash
git remote add someone https://github.com/SOMEONE/gudhi-devel.git
+```
## Stay up-to-date
```bash
@@ -89,7 +93,7 @@ You may want to look at https://github.com/settings/notifications (and other set
Some bold reviewer might make changes to your branch. You will then need `git pull` for your local branch to reflect those.
## Your work is merged!
-Once your pull request has been closed (your branch merged), you can remove your branch, both locally
+Once your pull request has been closed (your branch merged), you can remove your branch, both locally and also the branch on your github fork:
```bash
git checkout master # or any other branch, but you cannot remove the branch you are currently in
git branch -d some-fancy-name # local branch delete
@@ -99,7 +103,7 @@ If you add @VincentRouvreau or @mglisse as collaborator (https://github.com/LOGI
## Keep in touch
Create a new branch and keep contributing!
+
Do not try to reuse an old branch that has already been merged.
Make sure you run the fetch command just before creating any new branch, so you don't base it on some outdated version of master.
You can also work on several branches at the same time, using `git checkout some-fancy-name` and `git checkout name-of-other-branch` to switch between them (commit before switching or things may get complicated).
-