Skip to content

Commit b497050

Browse files
authored
Merge pull request #3508 from Willi0728/patch-2
setting-exit-codes-for-actions.md C
2 parents 261dbbb + d7680ad commit b497050

1 file changed

Lines changed: 1 addition & 3 deletions

File tree

content/actions/creating-actions/setting-exit-codes-for-actions.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ type: 'how_to'
2323
Exit status | Check run status | Description
2424
------------|------------------|------------
2525
`0` | `success` | The action completed successfully and other tasks that depends on it can begin.
26-
Nonzero value | `failure` | Any other exit code indicates the action failed. When an action fails, all concurrent actions are canceled and future actions are skipped. The check run and check suite both get a `failure` status.
26+
Nonzero value (any integer but 0)| `failure` | Any other exit code indicates the action failed. When an action fails, all concurrent actions are canceled and future actions are skipped. The check run and check suite both get a `failure` status.
2727

2828
### Setting a failure exit code in a JavaScript action
2929

@@ -43,13 +43,11 @@ For more information, see "[Creating a JavaScript action](/articles/creating-a-j
4343

4444
If you are creating a Docker container action, you can set a failure exit code in your `entrypoint.sh` script. For example:
4545

46-
{% raw %}
4746
```
4847
if <condition> ; then
4948
echo "Game over!"
5049
exit 1
5150
fi
5251
```
53-
{% endraw %}
5452

5553
For more information, see "[Creating a Docker container action](/articles/creating-a-docker-container-action)."

0 commit comments

Comments
 (0)