From 92f6cb37d2b01473778ccf169905c5be48b9edbe Mon Sep 17 00:00:00 2001 From: Carlos Nieto Petinal Date: Thu, 19 Feb 2026 17:48:44 +0100 Subject: [PATCH] Document ! negation for services, flags, and codeowners in code coverage gates Co-Authored-By: Claude Sonnet 4.6 --- content/en/code_coverage/configuration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/code_coverage/configuration.md b/content/en/code_coverage/configuration.md index 29987f030e7..70b75027eb2 100644 --- a/content/en/code_coverage/configuration.md +++ b/content/en/code_coverage/configuration.md @@ -185,9 +185,9 @@ Each gate has the following fields: - `patch_coverage_percentage`: The minimum coverage percentage on code changed in the pull request. - `config` (required): Gate configuration options. Supported values: - `threshold` (required): The minimum coverage percentage (0-100). - - `services`: (optional) A list of service name patterns to scope the gate to. Use `*` as a wildcard. When set, coverage is evaluated separately for each matching service. - - `codeowners`: (optional) A list of code owner patterns to scope the gate to. Use `*` as a wildcard. When set, coverage is evaluated separately for each matching code owner. - - `flags`: (optional) A list of [flag][3] name patterns to scope the gate to. Use `*` as a wildcard. When set, coverage is evaluated separately for each matching flag. + - `services`: (optional) A list of service name patterns to scope the gate to. Use `*` as a wildcard. Prefix a value with `!` to exclude matching services. When set, coverage is evaluated separately for each matching service. + - `codeowners`: (optional) A list of code owner patterns to scope the gate to. Use `*` as a wildcard. Prefix a value with `!` to exclude matching code owners. When set, coverage is evaluated separately for each matching code owner. + - `flags`: (optional) A list of [flag][3] name patterns to scope the gate to. Use `*` as a wildcard. Prefix a value with `!` to exclude matching flags. When set, coverage is evaluated separately for each matching flag. ### Examples