Merge pull request #1729 from HuongNV13/update-git-urls-github

[docs] Replace git:// moodle.org URLs with GitHub HTTPS URLs

Author: safatshahin

docs/guides/git/index.md

@@ -119,7 +119,7 @@ To keep your public repository up-to-date, we will register the remote repositor
 To register the upstream remote use the following command in your Moodle installation root folder:
 
 ```
-git remote add upstream git://git.moodle.org/moodle.git
+git remote add upstream https://github.com/moodle/moodle.git
 ```
 
 The following commands can be used to keep the your forked Moodle branches at your GitHub repository synced with Moodle's upstream repository. You may wish to store them in a script so that you can run it every week after the upstream repository is updated.

general/development/process/testing/integrated-issues.md

@@ -22,7 +22,7 @@ Your first priority as a tester should be to finish testing on the day they have
 
 :::
 
-1. Pull latest integration from [git://git.moodle.org/integration.git](git://git.moodle.org/integration.git)
+1. Pull latest integration from [https://github.com/moodle/integration.git](https://github.com/moodle/integration.git)
 2. Test issue by following the **Testing instructions**
 3. Select `Pass test` or `Fail test` as appropriate, adding a short description of what was tested if not obvious
 4. If you find you cannot finish testing a particular issue, click `Stop testing` and let the Integration team know about it.
@@ -80,7 +80,7 @@ Moodle uses two Git repositories for its source code. Their names are moodle.git
 To obtain the code from the integration.git repository, follow the instructions at [Git for Administrators page](https://docs.moodle.org/dev/Git_for_Administrators_page). But instead of cloning from git://github.com/moodle/moodle.git, use
 
 ```git
-git clone git://git.moodle.org/integration.git
+git clone https://github.com/moodle/integration.git
 ```
 
 as the very first command.

general/development/process/testing/qa.md

@@ -24,7 +24,7 @@ Would you like to help with QA testing? If so, please make sure you have created
    - Only assign one issue at a time unless you plan to test a number of related issues within the next 24 hours. In other words, don't assign several issues to yourself then do nothing for several days. ;-)
    - The label `test_server_required` indicates issues that can't be tested on the QA testing site. The label `credentials_required` indicates that credentials such as an OAuth 2 service client ID and secret are required.
 2. When you are ready to start testing a particular test case, select the workflow action `Start Testing`. If you decide that you can't perform the test, then you just select the workflow action `Cancel testing` and the test will go back into the test backlog, available for testing.
-3. Using either the [Moodle QA Testing Site](https://qa.moodledemo.net/) or your own test site running the latest Moodle 4.2dev (available from Git on the integration/main branch git://git.moodle.org/integration.git) with [debugging](https://docs.moodle.org/dev/debugging) set to developer, perform each of the steps listed in the test.
+3. Using either the [Moodle QA Testing Site](https://qa.moodledemo.net/) or your own test site running the latest Moodle 4.2dev (available from Git on the integration/main branch https://github.com/moodle/integration.git) with [debugging](https://docs.moodle.org/dev/debugging) set to developer, perform each of the steps listed in the test.
 4. Please *attach screenshots of the steps where you verify or check something*.
 5. Please test using the currently supported Boost theme.
 6. Choose an appropriate workflow action:

general/development/tools/mdk.md

@@ -50,7 +50,7 @@ Check out MDK's [`scripts` folder](https://github.com/FMCorz/mdk/tree/master/mdk
 mkdir /dir/to/stable_24/moodle
 mkdir /dir/to/stable_24/moodledata
 ln -s /dir/to/stable_24/moodle /var/www/stable_24
-git clone git://git.moodle.org/moodle.git /dir/to/moodle
+git clone https://github.com/moodle/moodle.git /dir/to/moodle
 cd /dir/to/stable_24/moodle
 php admin/cli/install.php --wwwroot## "http://localhost/stable_24" --dataroot/dir/to/stable_24/moodledata --dbtype## pgsql --dbnamestable24 --dbuser## root --dbpassroot --dbhost## localhost --fullname"Stable 24 PostgreSQL" --shortname## stable_24 --adminuseradmin --adminpass=test --allow-unstable --agree-license --non-interactive
 vim config.php

versioned_docs/version-4.5/guides/git/index.md

@@ -119,7 +119,7 @@ To keep your public repository up-to-date, we will register the remote repositor
 To register the upstream remote use the following command in your Moodle installation root folder:
 
 ```
-git remote add upstream git://git.moodle.org/moodle.git
+git remote add upstream https://github.com/moodle/moodle.git
 ```
 
 The following commands can be used to keep the your forked Moodle branches at your GitHub repository synced with Moodle's upstream repository. You may wish to store them in a script so that you can run it every week after the upstream repository is updated.

versioned_docs/version-5.0/guides/git/index.md

@@ -119,7 +119,7 @@ To keep your public repository up-to-date, we will register the remote repositor
 To register the upstream remote use the following command in your Moodle installation root folder:
 
 ```
-git remote add upstream git://git.moodle.org/moodle.git
+git remote add upstream https://github.com/moodle/moodle.git
 ```
 
 The following commands can be used to keep the your forked Moodle branches at your GitHub repository synced with Moodle's upstream repository. You may wish to store them in a script so that you can run it every week after the upstream repository is updated.

versioned_docs/version-5.1/guides/git/index.md

@@ -119,7 +119,7 @@ To keep your public repository up-to-date, we will register the remote repositor
 To register the upstream remote use the following command in your Moodle installation root folder:
 
 ```
-git remote add upstream git://git.moodle.org/moodle.git
+git remote add upstream https://github.com/moodle/moodle.git
 ```
 
 The following commands can be used to keep the your forked Moodle branches at your GitHub repository synced with Moodle's upstream repository. You may wish to store them in a script so that you can run it every week after the upstream repository is updated.

versioned_docs/version-5.2/guides/git/index.md

@@ -119,7 +119,7 @@ To keep your public repository up-to-date, we will register the remote repositor
 To register the upstream remote use the following command in your Moodle installation root folder:
 
 ```
-git remote add upstream git://git.moodle.org/moodle.git
+git remote add upstream https://github.com/moodle/moodle.git
 ```
 
 The following commands can be used to keep the your forked Moodle branches at your GitHub repository synced with Moodle's upstream repository. You may wish to store them in a script so that you can run it every week after the upstream repository is updated.