From e726254a380f2a35a2fcf71143e96cb5987d8102 Mon Sep 17 00:00:00 2001 From: saurabh Date: Tue, 26 Aug 2025 00:18:42 +0530 Subject: Refs #36620 -- Added contributor documentation for code coverage reports. This was included in the original reverted patch: a89183e63844a937aacd3ddb73c4952ef869d2cc Follow-up to 26b0e2bb92caf2d16cabe455792350f20d6f42ca. --- docs/internals/contributing/writing-code/submitting-patches.txt | 3 +++ 1 file changed, 3 insertions(+) (limited to 'docs/internals/contributing/writing-code/submitting-patches.txt') diff --git a/docs/internals/contributing/writing-code/submitting-patches.txt b/docs/internals/contributing/writing-code/submitting-patches.txt index 841a2109dc..428acffba1 100644 --- a/docs/internals/contributing/writing-code/submitting-patches.txt +++ b/docs/internals/contributing/writing-code/submitting-patches.txt @@ -438,6 +438,9 @@ All code changes * If the change is backwards incompatible in any way, is there a note in the release notes (``docs/releases/A.B.txt``)? * Is Django's test suite passing? +* If there is a :ref:`code coverage report ` + comment on the pull request, have you reviewed the missing coverage in + context (considering database/platform-specific limitations)? * If the change affects the Django admin or rendered HTML output, has :ref:`accessibility testing ` been done? -- cgit v1.3