doc link tree problem

Author: Jannis-Mittenzwei

doc/developer_guide/developer_guide.rst

@@ -10,4 +10,4 @@
     ../design
     plugins
     modules/modules
-    ../user_guide/how_to_release
+    how_to_release

doc/developer_guide/how_to_release.rst

@@ -0,0 +1 @@
+.. include:: ../shared_content/how_release.rst

doc/shared_content/how_release.rst

@@ -0,0 +1,52 @@
+How to Release?
+===============
+
+Creating a Release
+++++++++++++++++++
+
+#. Prepare the project for a new release:
+
+    .. code-block:: shell
+
+        nox -s release:prepare -- [-h] [-v | --version VERSION] [-t | --type {major,minor,patch}]
+
+#. Merge your **Pull Request** to the **default branch**
+
+#. Trigger the release:
+
+    .. code-block:: shell
+
+        nox -s release:trigger
+
+What to do if the release failed?
++++++++++++++++++++++++++++++++++
+
+The release failed during pre-release checks
+--------------------------------------------
+
+#. Delete the local tag
+
+    .. code-block:: shell
+
+        git tag -d "${TAG}"
+
+#. Delete the remote tag
+
+    .. code-block:: shell
+
+        git push --delete origin "${TAG}"
+
+#. Fix the issue(s) which lead to the failing checks
+#. Start the release process from the beginning
+
+
+One of the release steps failed (Partial Release)
+-------------------------------------------------
+#. Check the Github action/workflow to see which steps failed
+#. Finish or redo the failed release steps manually
+
+.. note:: Example
+
+    **Scenario**: Publishing of the release on Github was successfully but during the PyPi release, the upload step got interrupted.
+
+    **Solution**: Manually push the package to PyPi

doc/user_guide/how_to_release.rst

@@ -1,52 +1 @@
-How to Release?
-===============
-
-Creating a Release
-++++++++++++++++++
-
-#. Prepare the project for a new release:
-
-    .. code-block:: shell
-
-        nox -s release:prepare -- [-h] [-v | --version VERSION] [-t | --type {major,minor,patch}]
-
-#. Merge your **Pull Request** to the **default branch**
-
-#. Trigger the release:
-
-    .. code-block:: shell
-
-        nox -s release:trigger
-
-What to do if the release failed?
-+++++++++++++++++++++++++++++++++
-
-The release failed during pre-release checks
---------------------------------------------
-
-#. Delete the local tag
-
-    .. code-block:: shell
-
-        git tag -d "${TAG}"
-
-#. Delete the remote tag
-
-    .. code-block:: shell
-
-        git push --delete origin "${TAG}"
-
-#. Fix the issue(s) which lead to the failing checks
-#. Start the release process from the beginning
-
-
-One of the release steps failed (Partial Release)
--------------------------------------------------
-#. Check the Github action/workflow to see which steps failed
-#. Finish or redo the failed release steps manually
-
-.. note:: Example
-
-    **Scenario**: Publishing of the release on Github was successfully but during the PyPi release, the upload step got interrupted.
-
-    **Solution**: Manually push the package to PyPi
+.. include:: ../shared_content/how_release.rst