Skip to content

Commit

Permalink
Update GitHub Actions Documentation for 'success' Expression (github#…
Browse files Browse the repository at this point in the history
  • Loading branch information
SoundaryaKoutharapu authored Oct 16, 2023
1 parent da4084a commit 7565ee8
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion content/actions/learn-github-actions/expressions.md
Original file line number Diff line number Diff line change
Expand Up @@ -319,7 +319,7 @@ You can use the following status check functions as expressions in `if` conditio

### success

Returns `true` when none of the previous steps have failed or been canceled.
Returns `true` when all previous steps have succeeded.

#### Example of `success`

Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
Use `jobs.<job_id>.needs` to identify any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails or is skipped, all jobs that need it are skipped unless the jobs use a conditional expression that causes the job to continue. If a run contains a series of jobs that need each other, a failure or skip applies to all jobs in the dependency chain from the point of failure or skip onwards.
Use `jobs.<job_id>.needs` to identify any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails or is skipped, all jobs that need it are skipped unless the jobs use a conditional expression that causes the job to continue. If a run contains a series of jobs that need each other, a failure or skip applies to all jobs in the dependency chain from the point of failure or skip onwards. If you would like a job to run even if a job it is dependent on did not succeed, use the `always()` conditional expression in `jobs.<job_id>.if`.

### Example: Requiring successful dependent jobs

Expand Down

0 comments on commit 7565ee8

Please sign in to comment.