-
Notifications
You must be signed in to change notification settings - Fork 11
/
exercise-guide.Rmd
61 lines (37 loc) · 3.11 KB
/
exercise-guide.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
---
author: "Thomas Oosterhuis and Dainius Masiliunas"
date: "`r format(Sys.time(), '%d %B, %Y')`"
pagetitle: "Exercise submission guide"
output:
knitrBootstrap::bootstrap_document:
theme: "simplex"
highlight: Tomorrow Night Bright
menu: FALSE
theme.chooser: TRUE
highlight.chooser: TRUE
---
# Exercise guide
Each morning tutorial is followed by an exercise in the afternoon. These daily exercises are made available each day on the [geoscripting-2020 organization](https://github.com/geoscripting-2020). This manual shows you how to obtain the repository, how to work on the exercise together with your teammate and how to submit and review other exercises.
## 1. Fork
First you need to *fork* the exercise repository. For an explanation of forking, see the [tutorial of lesson 1](http://geoscripting-wur.github.io/RProjectManagement/).
- Go to the [geoscripting-2020 organization](https://github.com/geoscripting-2020), and make sure your Github account is signed in and added to the organization
- Look for the repository named 'Exercise#-starter', where # is the lesson number of the day
- Open the repository by clicking on the name. Then, fork the repository by clicking on the *fork* button at the right-top of your screen
![fork button](https://github.com/PTOoster/Exercise-Guide/blob/master/images/fork_button.png?raw=true)
## 2. Add teammate and clone
Now you have your own version of the exercise repository, which you can clone to do the exercise on your computer. First you need to add your team member as collaborator to the repository.
- Go to settings, and click on *collaborators* in the menu on the left
- Add your team member by filling out their Github account name
- Clone the exercise (check the [tutorial of lesson 1](http://geoscripting-wur.github.io/RProjectManagement/))
- Work on the exercise and use Travis CI for feedback (check the Travis CI introduction)
![Add team member](https://github.com/PTOoster/Exercise-Guide/blob/master/images/team_member.png?raw=true)
## 3. Submit and review
Before the deadline, you submit your solution of the exercise via a *pull request*. Your exercise, and all exercises of the other teams, are then visible in the original repository on the [geoscripting-2020 organization](https://github.com/geoscripting-2020) under *pull requests*. Here you can review other teams.
- Push your final commits to your exercise repository
- Go to your repository on Github and click on *new pull request*
![pull request](https://github.com/PTOoster/Exercise-Guide/blob/master/images/pull_button.png?raw=true)
- Click on the button *create pull request*
- As subject of the pull request, write your team name, and click on the button *create pull request*
![Add team member](https://github.com/PTOoster/Exercise-Guide/blob/master/images/pull_request.png?raw=true)
- Go to the [geoscripting-2020 organization](https://github.com/geoscripting-2020). Under the tab *pull requests* you can now see the exercise repositories of all teams. To review, leave a comment under the pull request
![Add team member](https://github.com/PTOoster/Exercise-Guide/blob/master/images/review.png?raw=true)