...
 
Commits (2)
......@@ -80,13 +80,13 @@ you can **push** your changes to the remote.
- Open a terminal and go to the project directory.
- Run ```git add .```; note the space and period at the end of the command
This command adds your changes to a new **commit** (a set of changes).
If you change more things after running this command,
If you change more things after running this command,
run it again to add the newly made changes too.
- Run ```git commit -m "short description of the changes in this commit"```
The ```-m``` flag signals that you want to add a message to the commit.
The message is important when you want to find back these changes later on.
- Run ```git push origin master``` to push **your** commits to **git.wur.nl**.
Here, **origin** refers to the remote at git.wur.nl
Here, **origin** refers to the remote at git.wur.nl
and **master** refers to the branch on the remote that your changes apply to.
- Read the response in the terminal. Were you allowed to change the master branch at git.wur.nl?
......@@ -108,5 +108,4 @@ your identity is sent along with it.
This is how everybody knows who did what in the project.
## Step 5. Pulling changes from the remote
Once you have your local copy in place,
Once you have your local copy in place, you can make changes and commit those to the remote.