From 24c521651c7666d30cfe5e483767d292d1183ef1 Mon Sep 17 00:00:00 2001
From: Fran Garcia-Linares <fjgarlin@gmail.com>
Date: Tue, 28 Jan 2025 18:00:04 +0100
Subject: [PATCH] #3473000: Space in numbered list.
---
docs/info/validation-jobs.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/docs/info/validation-jobs.md b/docs/info/validation-jobs.md
index eb4ad1c9..e8a0a7f6 100644
--- a/docs/info/validation-jobs.md
+++ b/docs/info/validation-jobs.md
@@ -13,7 +13,7 @@ There are several code validation jobs, and these attempt to mirror what Drupal
By default, all validation jobs are allowed to fail. This means that even if a job reports failures, the overall result of the pipeline will not be affected by it. If there is a failure, the job will display an amber 'warning' instead of a red 'fail'.
-If a job is not allowed to fail then any reported problems will produce a red 'fail' and the overall pipeline status will be 'failed'.
+If a job is not allowed to fail then any reported problems will produce a red 'fail' and the overall pipeline status will be 'failed'.
There are several ways to alter this behavior, listed below.
@@ -49,9 +49,10 @@ cspell:
## Order of precedence
The `allow_failure` setting for a particular job is determined by the following order - the first match in this list takes priority:
+
1. The job-specific `_{name}_ALLOW_FAILURE` variable set in the UI pipeline form.
1. The job-specific variable as defined in the `.gitlab-ci.yml` file
1. `_ALL_VALIDATE_ALLOW_FAILURE` via the UI form
1. `_ALL_VALIDATE_ALLOW_FAILURE` in the `.gitlab-ci.yml`
1. The `allow_failure:` keyword setting for the job in `.gitlab-ci.yml`
-1. The `allow_failure:` keyword in the Gitlab Templates pipeline default.
+1. The `allow_failure:` keyword in the Gitlab Templates pipeline default.
--
GitLab