Replace always() with success() || failure() - #225
Merged
timtebeek merged 4 commits intoAug 25, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Add a recipe that replaces
always()in GitHub Actions job and step conditions withsuccess() || failure().Cover workflow files and composite action definitions.
Preserve operator precedence in larger expressions and avoid changing function-like text inside string literals.
Preserve block scalar formatting and update generated recipe metadata.
Add positive and negative tests for job conditions, step conditions, composite actions, multiline expressions, unrelated keys, and non-GitHub Actions YAML.
Fixes Replace
always()withsuccess() || failure()#42