actions-marketplace-validations/Await Check Suites
Wait for a commit's check suites to complete
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| repository | The commit's repository name with owner. For example, `jitterbit/await-check-suites`. | yes | ${{ github.repository }} |
| ref | The commit's ref (can be a SHA, branch name, or a tag name). | yes | ${{ github.sha }} |
| token | GitHub token for GitHub API requests. When `repository` is modified, set to a personal access token with access to `repository`. | yes | ${{ github.token }} |
| waitForACheckSuite | Wait for a check suite to be created if none exist. This is important to protect against race conditions if you know a check suite should exist on the `ref`'s commit. | yes | true |
| intervalSeconds | Number of seconds to wait between checks. | yes | 15 |
| timeoutSeconds | Number of seconds to wait before timing out. | no | — |
| failStepIfUnsuccessful | Fail step if any of the check suites complete with a conclusion other than 'success'. | yes | true |
| appSlugFilter | Filter check suites for a particular app's slug (e.g., 'github-actions'). | no | — |
| onlyFirstCheckSuite | Only take into account the first check suite ordered by the `created_at` timestamp. If `appSlugFilter` is set, only the first check suite that matches the app's slug is taken into account. This is important for scheduled workflows that only want to take into account pushed workflows. | yes | false |
Outputs
| name | description |
|---|---|
| conclusion | The combined conclusion of all check suites. |