[pitivi/sdk: 5/7] docs: Update URLs to code

[Alexandru Băluț <alexbalut src gnome org>]

commit 3b9622c015fbfb687fbe3c75e7151d4f0deed182
Author: Alexandru Băluț <alexandru balut gmail com>
Date:   Thu Nov 7 05:37:51 2019 +0100

    docs: Update URLs to code

 docs/Bug_reporting.md | 8 ++++----
 docs/HACKING.md       | 2 +-
 docs/Testing.md       | 6 +++---
 docs/releases/0.91.md | 2 +-
 4 files changed, 9 insertions(+), 9 deletions(-)
---
diff --git a/docs/Bug_reporting.md b/docs/Bug_reporting.md
index 2b97b589..2e08a794 100644
--- a/docs/Bug_reporting.md
+++ b/docs/Bug_reporting.md
@@ -161,10 +161,10 @@ gdb python3 -ex "run $(which pitivi)"
 
 ## Debug logs
 
-When you need to know what’s going on inside pitivi, you can launch it
+When you need to know what’s going on inside Pitivi, you can launch it
 with a debug level. In
-[loggable.py](https://git.gnome.org/browse/pitivi/tree/pitivi/utils/loggable.py#n50),
-there are five levels: ( <span style="color:red;">ERROR</span>,
+[loggable.py](https://gitlab.gnome.org/GNOME/pitivi/blob/master/pitivi/utils/loggable.py#L61),
+there are six levels: ( <span style="color:red;">ERROR</span>,
 <span style="color:yellow; background-color:gray;">WARN</span>,
 <span style="color:magenta;">FIXME</span>,
 <span style="color:green;">INFO</span>,
@@ -225,7 +225,7 @@ In the rare cases where a performance problem is caused by our UI code,
 you can profile Pitivi itself, with this command (and yes,
 `JUMP_THROUGH_HOOPS` is needed for this case, it is an environment
 variable of
-[bin/pitivi](https://git.gnome.org/browse/pitivi/tree/bin/pitivi.in):
+[bin/pitivi](https://gitlab.gnome.org/GNOME/pitivi/blob/master/bin/pitivi.in):
 
 ```
 JUMP_THROUGH_HOOPS=1 python3 -m cProfile -s time -o pitivi_performance.profile bin/pitivi
diff --git a/docs/HACKING.md b/docs/HACKING.md
index 8ddea938..355b7175 100644
--- a/docs/HACKING.md
+++ b/docs/HACKING.md
@@ -86,7 +86,7 @@ To update the dependencies installed in the sandbox, run:
 That will actually recreate the sandbox prefix, updating all
 dependencies from their git repos and tarballs as defined in the
 [flatpak
-manifest](https://git.gnome.org/browse/pitivi/tree/build/flatpak/pitivi.template.json) (located at 
`build/flatpak/pitivi.template.json`).
+manifest](https://gitlab.gnome.org/GNOME/pitivi/blob/master/build/flatpak/org.pitivi.Pitivi.json).
 
 
 ### How we use the sandbox
diff --git a/docs/Testing.md b/docs/Testing.md
index 71a67677..1be92ba2 100644
--- a/docs/Testing.md
+++ b/docs/Testing.md
@@ -49,14 +49,14 @@ come in our [IRC channel](http://www.pitivi.org/?go=contact)!
 ## Integration tests
 
 The integration tests are run with GstValidate. They are located in the
-[tests/validate-tests](https://git.gnome.org/browse/pitivi/tree/tests/validate-tests)
+[tests/validate-tests](https://gitlab.gnome.org/GNOME/pitivi/tree/master/tests/validate-tests)
 directory. Each `.scenario` file in the
-[scenarios](https://github.com/pitivi/pitivi/tree/master/tests/validate-tests/scenarios)
+[scenarios](https://gitlab.gnome.org/GNOME/pitivi/tree/master/tests/validate-tests/scenarios)
 subdirectory contains a sequence of actions which represent a test.
 
 When a test is run, the actions in the scenario are performed by
 handlers in
-[pitivi/utils/validate.py](https://github.com/pitivi/pitivi/blob/master/pitivi/utils/validate.py),
+[pitivi/utils/validate.py](https://gitlab.gnome.org/GNOME/pitivi/blob/master/pitivi/utils/validate.py),
 or by handlers in GES. The handlers generally act on the widgets and
 check the expected effect has been obtained on the GES objects. Besides
 the checks integrated in the handlers, for now it is not possible to
diff --git a/docs/releases/0.91.md b/docs/releases/0.91.md
index 9b1156da..3a52e39f 100644
--- a/docs/releases/0.91.md
+++ b/docs/releases/0.91.md
@@ -103,7 +103,7 @@ details and historical context.
 -   A revised and simplified API has been implemented in GES and
     integrated in Pitivi.
 -   A small [brand
-    adjustment](https://git.gnome.org/browse/pitivi/commit/?id=549e1e3b).
+    adjustment](https://gitlab.gnome.org/GNOME/pitivi/commit/549e1e3b).
     From now on, PiTiVi should simply be called “Pitivi”.
 -   Dependencies are defined and checked in only one, centralized place:
     check.py