Skip to content

Commit ac64e41

Browse files
claireguyotteo
authored andcommitted
[doc][core] Wording corrections after PR review.
1 parent fef2531 commit ac64e41

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

docs/handbook/configuration.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
Any task in a workflow can be declared as non-critical. A non-critical task is a task that doesn't trigger a global environment ERROR in case of failure. The state of a non-critical task doesn't affect the environment state in any way.
66

7-
To declare a task as non-critical, a line has to be added in the corresponding workflow template. Under the task role, in the `task` section (usually after the `load` statement), the line to add is `critical: false`, like in the following example:
7+
To declare a task as non-critical, a line has to be added in the task role block within a workflow template file. Specifically, in the task section of such a task role (usually after the `load` statement), the line to add is `critical: false`, like in the following example:
88

99
```yaml
1010
roles:
@@ -14,4 +14,6 @@ roles:
1414
task:
1515
load: mytask
1616
critical: false
17-
```
17+
```
18+
19+
In the absence of an explicit `critical` trait for a given task role, the assumed default value is `critical: true`.

0 commit comments

Comments
 (0)