Skip to content

Commit 3c9e623

Browse files
authored
setting-exit-codes-for-actions.md C
1 parent f0e7705 commit 3c9e623

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
@@ -21,7 +21,7 @@ type: 'how_to'
2121
Exit status | Check run status | Description
2222
------------|------------------|------------
2323
`0` | `success` | The action completed successfully and other tasks that depends on it can begin.
24-
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.
24+
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.
2525

2626
### Setting a failure exit code in a JavaScript action
2727

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

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

44-
{% raw %}
4544
```
4645
if <condition> ; then
4746
echo "Game over!"
4847
exit 1
4948
fi
5049
```
51-
{% endraw %}
5250

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

0 commit comments

Comments
 (0)