From 8e244b441fee6cfac2e71c46c5e3ee48f6bcd666 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=BCrgen=20Gmach?= Date: Sat, 14 Oct 2023 17:15:42 +0200 Subject: [PATCH] Convert links within this documenation to relative links So they will work also after the migration. --- explanation/performance.rst | 4 ++-- how-to/contributing-changes.rst | 14 +++++--------- 2 files changed, 7 insertions(+), 11 deletions(-) diff --git a/explanation/performance.rst b/explanation/performance.rst index 5babc58..baf5e72 100644 --- a/explanation/performance.rst +++ b/explanation/performance.rst @@ -69,7 +69,8 @@ You should also make use of the already mentioned ``cachedproperty`` decorator in order to avoid querying the database more often then necessary. When changing code, it can easily happen to increase the query count. You can -avoid this by using a helper to `preserve query count`_. +avoid this by using a helper to +:doc:`preserve query count <../how-to/preserve-query-count>`. When you face performance or even timeout issues, you should learn more about `timeout analysis`_ (internal video). @@ -79,7 +80,6 @@ PostGreSQL comes with a `builtin tool`_ to analyze SQL queries. .. _timeout analysis: https://drive.google.com/file/d/1hUivL07Msoyej3wd_T4hMAX61EJzfE38/view?usp=drive_link .. _builtin tool: https://www.postgresql.org/docs/current/sql-explain.html .. _write efficient queries: https://dev.launchpad.net/Database/Performance -.. _preserve query count: https://launchpad.readthedocs.io/en/latest/how-to/preserve-query-count.html Delivering payload ------------------ diff --git a/how-to/contributing-changes.rst b/how-to/contributing-changes.rst index 75592e3..968a016 100644 --- a/how-to/contributing-changes.rst +++ b/how-to/contributing-changes.rst @@ -34,19 +34,15 @@ Create a branch from a reasonable point, such as ``master``. git checkout -b my-change Make your changes on the branch. Be sure to test them locally by setting up a -local `Launchpad development instance`_. - -.. _Launchpad development instance: https://launchpad.readthedocs.io/en/latest/how-to/running.html +local :doc:`Launchpad development instance `. Run the pre-commit hook ----------------------- -If you followed the instructions to `set up and run Launchpad`_, you should -already have ``pre-commit`` installed and have the ``pre-commit`` git hook -`installed`_. If not, complete these steps before proceeding. - -.. _set up and run Launchpad: https://launchpad.readthedocs.io/en/latest/how-to/running.html -.. _installed: https://launchpad.readthedocs.io/en/latest/how-to/running.html#installing-the-pre-commit-hook +If you followed the instructions to :doc:`set up and run Launchpad `, +you should already have ``pre-commit`` installed and have the +:ref:`pre-commit git hook ` installed. If not, complete these steps +before proceeding. Push your changes --------------------