Find information on the steps GitHub takes to cancel a workflow run.
When canceling a workflow run, you may be running other software that uses resources related to the workflow run. To help you free up resources related to the workflow run, it may help to understand the steps GitHub performs to cancel a workflow run.
if
conditions for all currently running jobs. If the condition evaluates to true
, the job will not get canceled. For example, the condition if: always()
would evaluate to true and the job continues to run. When there is no condition, that is the equivalent of the condition if: success()
, which only runs if the previous step finished successfully.if
conditions for the unfinished steps. If the condition evaluates to true
, the step continues to run. You can use the cancelled
expression to apply a status check of cancelled()
. For more information, see Evaluate expressions in workflows and actions.SIGINT/Ctrl-C
to the step's entry process (node
for JavaScript actions, docker
for container actions, and bash/cmd/pwd
when using run
in a step). If the process doesn't exit within 7500 ms, the runner will send SIGTERM/Ctrl-Break
to the process, then wait for 2500 ms for the process to exit. If the process is still running, the runner kills the process tree.RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4