Skip to content

Commit f96969d

Browse files
authored
Update README.md
1 parent 4a910e5 commit f96969d

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

README.md

+6-2
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,10 @@ git config --global user.email "YourEmail"
2323

2424
# Exercise 1
2525

26+
clone this repository!
27+
28+
# Exercise 2
29+
2630
We have a separate directory for each group.
2731

2832
Please write a markdown file with short **introduction** about yourself. For example, what food do you like.
@@ -31,7 +35,7 @@ Save it with your name or your pseudonym like `yourname.md`, and add it to the d
3135

3236
Pull, Commit, Push and Pull to add your introduction - and also to get the introductions of the others.
3337

34-
# Exercise 2
38+
# Exercise 3
3539

3640
In each group directory there is a `README.md` file in which we want to collect **recommendations of movies and/or TV shows**.
3741

@@ -41,7 +45,7 @@ Commit and push...
4145

4246
As you are all doing this at (more or less) the same time, it is very likely that there will be merge conflicts and that chaos will ensue... breathe in and breathe out, and let's try to work these out together. Collaborating and social coding is not only about jointly contributing to a repository, but also on making agreements on the workflow. Who does what, in what order, and who takes responsibility.
4347

44-
# Exercise 3
48+
# Exercise 4
4549

4650
Create an [issue](https://github.com/Donders-Institute/git-workshop/issues) for one of your group members, for example ask them to add or modify a file. Assign a label to the issue and assign it to the group member that should resolve it.
4751

0 commit comments

Comments
 (0)