Document required checks for code coverage uploads (#63566)

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copilot-Session: 1a963a64-6e69-44a5-9f76-aa6d086f4af3

Author: joshhale

content/code-security/how-tos/maintain-quality-code/restrict-code-coverage.md

@@ -1,7 +1,7 @@
 ---
 title: Setting code coverage thresholds for pull requests
 shortTitle: Set coverage thresholds
-intro: Protect your code coverage by automatically blocking pull requests that fall below the coverage levels your team requires.
+intro: Prevent pull requests from being merged when uploaded code coverage falls below the levels your team requires.
 allowTitleToDifferFromFilename: true
 versions:
   feature: code-quality
@@ -14,14 +14,19 @@ category:
 > [!NOTE]
 > This feature is in {% data variables.release-phases.public_preview %} and subject to change.
 
+## How the code coverage rule works
+
+The **Restrict code coverage** rule evaluates uploaded line coverage data against the configured thresholds. It does not wait for coverage uploads to complete.
+
+To prevent a pull request from being merged before all expected coverage results are available, make each status check associated with an expected coverage upload a required status check. This includes coverage uploaded from separate jobs or workflows.
+
+For more information about line coverage, see [AUTOTITLE](/code-security/reference/code-quality/code-coverage).
+
 ## Prerequisites
 
 * {% data variables.product.prodname_code_quality %} is enabled on the repository.
 * Code coverage data is uploaded to {% data variables.product.github %} for the pull request branch. See [AUTOTITLE](/code-security/how-tos/maintain-quality-code/set-up-code-coverage).
 
-> [!NOTE]
-> Coverage thresholds are evaluated against **line coverage**. See [AUTOTITLE](/code-security/reference/code-quality/code-coverage).
-
 ## Creating a coverage threshold rule
 
 {% data reusables.repositories.navigate-to-repo %}

content/code-security/how-tos/maintain-quality-code/set-up-code-coverage.md

@@ -25,6 +25,9 @@ You can set up code coverage for your repository in two ways:
   * You have complex CI requirements (such as private registries or custom build steps).
   * You want to understand exactly how coverage is configured.
 
+> [!IMPORTANT]
+> If you use the **Restrict code coverage** rule, make each status check associated with an expected coverage upload a required status check. For more information, see [How the code coverage rule works](/code-security/how-tos/maintain-quality-code/restrict-code-coverage#how-the-code-coverage-rule-works).
+
 ## Automatic setup
 
 You can use the automatic setup option to generate a working code coverage workflow without manually authoring CI configuration. An agent analyzes your repository, identifies your test framework, and opens a pull request with a coverage workflow ready for review.

content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md

@@ -254,6 +254,8 @@ For more information, see [AUTOTITLE](/code-security/concepts/code-quality/code-
 
 If your repository has {% data variables.product.prodname_code_quality %} enabled and code coverage data is being uploaded, you can use rulesets to prevent pull requests from being merged based on code coverage thresholds. For more information about uploading coverage data, see [AUTOTITLE](/code-security/how-tos/maintain-quality-code/set-up-code-coverage).
 
+The rule evaluates only coverage data that has already been uploaded and does not wait for coverage uploads to complete. To ensure that all expected coverage results are evaluated before a pull request can be merged, make each status check associated with an expected coverage upload a required status check.
+
 This rule blocks a pull request from being merged when either of two code coverage thresholds is not met:
 
 * **Minimum line coverage percentage**: the aggregated line coverage for the pull request branch is below the configured percentage.