Change URLs

project/README.md

@@ -19,10 +19,10 @@ It is very simple, only consists in a couple of files written in bash and you wi
 
 In this tutorial you will learn how to make commits in the Git project, to create several branches, to push things to Gogs, and to follow a standard procedure to develop collaboratively. Afterwards, you should apply the same methods to any other collaborative development inside the ELIC department. The objectives will be achieved gradually following these topics:
 
-1.     [Set up your working environment](http://www.climate.be:3000/TECLIM/Git_Training/src/master/project/working_environment)
-2.     [Prepare issues on Gogs](http://www.climate.be:3000/TECLIM/Git_Training/src/master/project/gogs_issues)
-3.     [Prepare branches](http://www.climate.be:3000/TECLIM/Git_Training/src/master/project/branches)
-4.     [Add new functions](http://www.climate.be:3000/TECLIM/Git_Training/src/master/project/functions)
-5.     [Create pull request](http://www.climate.be:3000/TECLIM/Git_Training/src/master/project/pull_request)
-6.     [Review and test others' branches](http://www.climate.be:3000/TECLIM/Git_Training/src/master/project/review)
-7.     [Pull master changes](http://www.climate.be:3000/TECLIM/Git_Training/src/master/project/pull_master)
+1.     [Set up your working environment](https://www.elic.ucl.ac.be/TECLIM/Git_Training/src/master/project/working_environment)
+2.     [Prepare issues on Gogs](https://www.elic.ucl.ac.be/TECLIM/Git_Training/src/master/project/gogs_issues)
+3.     [Prepare branches](https://www.elic.ucl.ac.be/TECLIM/Git_Training/src/master/project/branches)
+4.     [Add new functions](https://www.elic.ucl.ac.be/TECLIM/Git_Training/src/master/project/functions)
+5.     [Create pull request](https://www.elic.ucl.ac.be/TECLIM/Git_Training/src/master/project/pull_request)
+6.     [Review and test others' branches](https://www.elic.ucl.ac.be/TECLIM/Git_Training/src/master/project/review)
+7.     [Pull master changes](https://www.elic.ucl.ac.be/TECLIM/Git_Training/src/master/project/pull_master)

project/functions/README.md

@@ -24,7 +24,7 @@ git commit -m "message explaining what you have done. Fixes issue #issue_number"
 
 When we run `git commit`, Git takes everything we have told it to save by using `git add` and stores a copy permanently inside the special `.git` directory. This permanent copy is called a commit (or revision) and its short identifier is `f22b25e` (Your commit may have another identifier.)
 
-You can do as many commits as you wish while developing your function. If you reach a point at which any of the open issues gets solved, you can make your commit message end with `Fixes #issue_number` ([Exercise 4 – Open new issue in Git_Training project](http://www.climate.be:3000/TECLIM/Git_Training/src/master/project/gogs_issues)).
+You can do as many commits as you wish while developing your function. If you reach a point at which any of the open issues gets solved, you can make your commit message end with `Fixes #issue_number` ([Exercise 4 – Open new issue in Git_Training project](https://www.elic.ucl.ac.be/TECLIM/Git_Training/src/master/project/gogs_issues)).
 
 If you don't specify the `-m` parameter a text editor will open automatically to allow you to write the commit message.
 

project/pull_master/README.md

@@ -4,7 +4,7 @@ Once the project coordinator has accepted all pull requests, there is a new vers
 
 ## Exercise 13 - Update master branch
 
-Following instruction from [Exercise 10 – Checkout a branch from Git_Training project](http://www.climate.be:3000/TECLIM/Git_Training/src/master/project/review), checkout the master branch.
+Following instruction from [Exercise 10 – Checkout a branch from Git_Training project](https://www.elic.ucl.ac.be/TECLIM/Git_Training/src/master/project/review), checkout the master branch.
 
 ```
 git checkout master