Skip to content

Commit 9e9a140

Browse files
committed
clarify better when to clone and when to fork; closes #289
1 parent 8a00e39 commit 9e9a140

1 file changed

Lines changed: 12 additions & 0 deletions

File tree

content/concepts.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,18 @@ working with a git repository to which you do not have write access.
6969
whereas forking is a particular operation implemented on GitHub/GitLab.
7070

7171

72+
## Should we clone or fork?
73+
74+
Should we all work on forks or should we all work inside one repository?
75+
76+
- For most small or medium-sized research projects you probably want to **work by
77+
cloning a repository** that all research group has write access to (we will
78+
exercise this in the next section).
79+
80+
- It's only when you want to contribute to a project that you don't have write
81+
access to that you need to use **forks** (we will practice this as well).
82+
83+
7284
## Generating from templates
7385

7486
A repository can be marked as **template** and new repositories can be

0 commit comments

Comments
 (0)