diff --git a/2022/2022-05-31_git-trilogy-part-1/slides/forks.md b/2022/2022-05-31_git-trilogy-part-1/slides/forks.md index 6246558f2695d77e929501efd5b27059dd015ed7..f958de248538688433e3f2fd35197eeab3fde2a9 100644 --- a/2022/2022-05-31_git-trilogy-part-1/slides/forks.md +++ b/2022/2022-05-31_git-trilogy-part-1/slides/forks.md @@ -20,18 +20,15 @@ # New term: <font color="color:red">fork</font> ## What is a `fork`? -- In general, by default you can only **read** files in a repository. -- In general, by default you **cannot write** changes. +- In general, by default, you can only **read** files in a repository. You **cannot write**. <div class="fragment"> <img src="slides/img/forking.png" height="400px"> -- You have to work on your **own copy** of the repository +- You have to work on your **own copy** of the repository in order to make changes. - In other words, you have to work on your own <font color="red">**fork**</font>. -<br> -## Why? @@ -39,7 +36,9 @@ Browse to the original repository and click on the button `Fork`: -<img src="https://docs.gitlab.com/ee/user/project/repository/img/forking_workflow_fork_button_v13_10.png" height="250px"> +<div align="center"> +<img src="https://docs.gitlab.com/ee/user/project/repository/img/forking_workflow_fork_button_v13_10.png" height="150"> +</div> <br> @@ -48,19 +47,19 @@ Browse to the original repository and click on the button `Fork`: ## Time to practice! -1. Fork the practice repository: <br><br> -TODO<br><br> +1. Fork the training repository [https://gitlab.lcsb.uni.lu/R3/school/git/basic-practice-pages](https://gitlab.lcsb.uni.lu/R3/school/git/basic-practice-pages) + + +Congrats! Now you have your own **fork**! -Congrats! Now you have your own **fork**! +# How to update my fork? -# How to update my fork? - TODO: move to the end or delete -\ -As you have your own fork, it will not automatically be updated once the original repository is updated. +As you have your own copy (fork), it will not automatically be updated once the original repository is updated.  You have to update it yourself! <br> -**More on that later!** +**More on that later - time permitting** diff --git a/2022/2022-05-31_git-trilogy-part-1/slides/gitlab.md b/2022/2022-05-31_git-trilogy-part-1/slides/gitlab.md index dc042490d5ed684ae6aa99a720f23b3b451bb8f4..e33663a55263a0cf9afd055e05630fc16cca2d3c 100644 --- a/2022/2022-05-31_git-trilogy-part-1/slides/gitlab.md +++ b/2022/2022-05-31_git-trilogy-part-1/slides/gitlab.md @@ -28,16 +28,9 @@ Another popular platforms: 1. Login to [https://gitlab.lcsb.uni.lu](https://gitlab.lcsb.uni.lu) * use your LUMS credentials -2. browse the existing repositories - * Explore -> - * navigate to the training repository +2. Browse the existing repositories + * Explore and Search + * Navigate to the training repository [https://gitlab.lcsb.uni.lu/R3/school/git/basic-practice-pages](https://gitlab.lcsb.uni.lu/R3/school/git/basic-practice-pages) 3. Inspect project/repository folder structure -4. Discover an issue (see README.md) and report it +4. Report an issue -<div class="fragment"> - -Congrats! You are a **reporter** :) -</div> - -notes: -- reporter is very important role