Draft: Add minimum coverage threshold to Coverage-Check approval rule (Docs)

Norman Debaldrequested to merge
gitlab-community/gitlab-org/gitlab:6284-enforce-minimum-coverage-threshold-docs into master

What does this MR do and why?

This is MR 3 of 3 implementing the minimum coverage threshold feature for #6284:

  1. Backend - Database, service logic, REST API, GraphQL, blockage reason (!224343 (closed))
  2. Frontend - Settings UI, MR widget feedback, blockage reason display (!224368 (closed))
  3. Documentation (this MR)

Problem

After the backend (!224343 (closed)) and frontend (!224368 (closed)) added the coverage_minimum_threshold field and blockage reason display, the user-facing documentation and API reference do not describe the new capability.

Solution

Updates documentation across three files to describe the new optional minimum coverage threshold on Coverage-Check approval rules.

Changes

Area Details
Code coverage docs Expand "Add a coverage check approval rule" section with threshold configuration step, blocking conditions list, and MR widget feedback description (doc/ci/testing/code_coverage/_index.md)
API docs Add coverage_minimum_threshold parameter to Create and Update project approval rule endpoint tables (doc/api/merge_request_approvals.md)
Approvals overview Update required approvals reference to mention minimum threshold (doc/user/project/merge_requests/approvals/_index.md)

References

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist.

  • The change is documentation only, no code changes.
  • All three documentation files updated consistently describe the same feature behavior.
  • API parameter documentation matches the implementation in !224343 (closed) (type: float, optional, 0-100, code_coverage rules only).
  • No auto-generated files modified (GraphQL reference and OpenAPI specs are already updated by !224343 (closed)).

Related to #6284

Merge request reports