mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-24 14:16:09 +00:00
Code Issues 32 Releases Wiki Activity

Replaced :doc: role usage with :ref: when appropriate in docs.

Browse Source
This commit is contained in:
Natalia
2025-08-27 18:36:01 -03:00
committed by nessita
parent a9fe98d5bd
commit ae03f81ffa
10 changed files with 41 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/internals/contributing/bugs-and-features.txt
View File

@@ -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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

4
docs/internals/contributing/localizing.txt
View File

@@ -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

2
docs/internals/contributing/new-contributors.txt
View File

@@ -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
------------------------

8
docs/internals/contributing/triaging-tickets.txt
View File

@@ -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.

2
docs/internals/contributing/writing-code/working-with-git.txt
View File

@@ -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