jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Update GitHub Actions Documentation for 'success' Expression (#29186)

Browse Source
This commit is contained in:
Soundarya Koutharapu
2023-10-17 03:32:52 +05:30
committed by GitHub
parent da4084a168
commit 7565ee8cfd
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/actions/learn-github-actions/expressions.md
View File

@@ -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`

2
data/reusables/actions/jobs/section-using-jobs-in-a-workflow-needs.md
View File

@@ -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