From 417a201110710c729179691637376c508f525c45 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Asbj=C3=B8rn=20Ulsberg?= Date: Wed, 17 Jun 2026 11:19:24 +0200 Subject: [PATCH] Label is not optional The `label` property of `actions/upload-code-coverage` is not optional. --- .../how-tos/maintain-quality-code/set-up-code-coverage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/code-security/how-tos/maintain-quality-code/set-up-code-coverage.md b/content/code-security/how-tos/maintain-quality-code/set-up-code-coverage.md index 51d909e34a20..214f1c84f51b 100644 --- a/content/code-security/how-tos/maintain-quality-code/set-up-code-coverage.md +++ b/content/code-security/how-tos/maintain-quality-code/set-up-code-coverage.md @@ -60,7 +60,7 @@ After your tests generate a Cobertura XML report, upload it to {% data variables 1. Replace the following values: * **`COVERAGE-FILE-PATH.xml`**: The path to your Cobertura XML report (for example, `coverage.xml` or `target/site/jacoco/cobertura.xml`). * **`LANGUAGE`**: The primary language of the code being covered (for example, `Python`, `Java`, `JavaScript`). - * **`LABEL`**: An optional label to identify this coverage report (for example, `code-coverage/pytest`). + * **`LABEL`**: A label to identify this coverage report (for example, `code-coverage/pytest`). 1. Commit and push the workflow change. ### Full workflow example