Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update expression #791

Merged
merged 1 commit into from
Feb 8, 2023
Merged

docs: update expression #791

merged 1 commit into from
Feb 8, 2023

Conversation

yeikel
Copy link
Contributor

@yeikel yeikel commented Feb 7, 2023

if a job is aborted or suffers a critical failure, always() is not appropriate

always
Causes the step to always execute, and returns true, even when canceled. The always expression is best used at the step level or on tasks that you expect to run even when a job is canceled. For example, you can use always to send logs even when a job is canceled.

Note: Avoid using always for any task that could suffer from a critical failure, for example: getting sources, otherwise the workflow may hang until it times out. If you want to run a job or step regardless of its success or failure, use the recommended alternative:if: success() || failure()

Source: https://docs.github.com/en/actions/learn-github-actions/expressions#always

@mikepenz
Copy link
Owner

mikepenz commented Feb 8, 2023

Thank you very much for the PR

@mikepenz mikepenz merged commit e97c202 into mikepenz:main Feb 8, 2023
@mikepenz mikepenz added the other label Feb 8, 2023
@yeikel yeikel deleted the patch-1 branch February 8, 2023 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants