diff options
Diffstat (limited to 'docs/internals')
5 files changed, 10 insertions, 8 deletions
diff --git a/docs/internals/contributing/bugs-and-features.txt b/docs/internals/contributing/bugs-and-features.txt index d117b2e165..146603e226 100644 --- a/docs/internals/contributing/bugs-and-features.txt +++ b/docs/internals/contributing/bugs-and-features.txt @@ -55,7 +55,7 @@ particular: as they are filed. To understand the lifecycle of your ticket once you have created it, refer to -:doc:`triaging-tickets`. +:ref:`triage-workflow`. Reporting user interface bugs ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/internals/contributing/localizing.txt b/docs/internals/contributing/localizing.txt index 112a74dd9e..59a60a6a4c 100644 --- a/docs/internals/contributing/localizing.txt +++ b/docs/internals/contributing/localizing.txt @@ -61,8 +61,8 @@ the date, time and numbers formatting particularities of your locale. See The format files aren't managed by the use of Transifex. To change them, you must: -* :doc:`Create a pull request<writing-code/submitting-patches>` against the - Django Git ``main`` branch, as for any code change. +* :ref:`Create a pull request <patch-review-checklist>` against the Django Git + ``main`` branch, as for any code change. * Open a ticket in Django's ticket system, set its ``Component`` field to ``Translations``, set the "has patch" flag, and include the link to the pull diff --git a/docs/internals/contributing/new-contributors.txt b/docs/internals/contributing/new-contributors.txt index 3ec74b6bd4..a6bb17ceeb 100644 --- a/docs/internals/contributing/new-contributors.txt +++ b/docs/internals/contributing/new-contributors.txt @@ -47,7 +47,7 @@ Keep old patches up-to-date Oftentimes the codebase will change between a patch being submitted and the time it gets reviewed. Make sure it still applies cleanly and functions as expected. Updating a patch is both useful and important! See more on -:doc:`writing-code/submitting-patches`. +:ref:`patch-review-checklist`. Write some documentation ------------------------ diff --git a/docs/internals/contributing/triaging-tickets.txt b/docs/internals/contributing/triaging-tickets.txt index c54065ea22..295bf25ee5 100644 --- a/docs/internals/contributing/triaging-tickets.txt +++ b/docs/internals/contributing/triaging-tickets.txt @@ -29,11 +29,13 @@ confusion or disagreement. Django is a community project, and every contribution helps. We can't do this without **you**! +.. _triage-workflow: + Triage workflow =============== Unfortunately, not all reports in the ticket tracker provide all the -:doc:`required details<bugs-and-features>`. A number of tickets have proposed +:ref:`required details <reporting-bugs>`. A number of tickets have proposed solutions, but those don't necessarily meet all the requirements :ref:`adhering to the guidelines for contributing <patch-style>`. @@ -168,8 +170,8 @@ Has patch --------- This means the ticket has an associated solution. These will be reviewed to -ensure they adhere to the :doc:`documented guidelines -<writing-code/submitting-patches>`. +ensure they adhere to the :ref:`documented guidelines +<patch-review-checklist>`. The following three fields (Needs documentation, Needs tests, Patch needs improvement) apply only if a patch has been supplied. diff --git a/docs/internals/contributing/writing-code/working-with-git.txt b/docs/internals/contributing/writing-code/working-with-git.txt index 579543f876..7209bc0624 100644 --- a/docs/internals/contributing/writing-code/working-with-git.txt +++ b/docs/internals/contributing/writing-code/working-with-git.txt @@ -4,7 +4,7 @@ Working with Git and GitHub This section explains how the community can contribute code to Django via pull requests. If you're interested in how :ref:`mergers <mergers-team>` handle -them, see :doc:`../committing-code`. +them, see :ref:`handling-pull-requests`. Below, we are going to show how to create a GitHub pull request containing the changes for Trac ticket #xxxxx. By creating a fully-ready pull request, you |