# What is a `fork`?
# Not really ...
# What is a `fork`? - In general, when contributing to a repository, you only have **read** access. - In other words, you can only **pull** (unless it is your own repository or access has been granted). - In general, you **cannot write** changes. In other words, you do not have **push** access. - You have to work on your **own copy**. - In other words, you have to work on your own **fork**. # How to get a fork? Browse to the original repository and click on the button `Fork`: ![Fork the repo](https://help.github.com/assets/images/help/repository/fork_button.jpg) # Time to practice! Fork the practice repository:

https://git-r3lab.uni.lu/R3/school/git/basic-practice-pages

Then, clone your fork to your home directory! ```bash $ git clone ssh://git@git-r3lab-server.uni.lu:8022//basic-practice-pages.git ``` Change to the practice directory with: ```bash $ cd basic-practice-pages ``` # A note on shortcuts ... Any other rudimentary method such as *'I simply download the `.zip` and unzip it - works like a charm!'* shall **be avoided**! **Why?** # How to update my fork? As you have your own fork, it will not automatically be updated once the original repository is updated. ![bulb](slides/img/bulb.png) You have to update it yourself!
**More on that later!**