A look at lewagon/wait-on-check-action: 395 stars on GitHub, written primarily in Ruby. Pause until a job in another workflow completes successfully.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Pause until a job in another workflow completes successfully.
This action uses GitHub's Checks API to poll for check results. On success, the action exits allowing the workflow to resume. Otherwise, the action exits with status code 1 and fails the workflow.
[!TIP]
Prefer to skip the Ruby setup overhead? wait-on-check-action-ts is a TypeScript port that runs as a native node24 action with no setup step, while keeping the same parameters, defaults, and behavior.
When to use this action
You need to wait for checks on non-default branches (PRs, feature branches)
You need multiple workflows to wait atomically until all checks pass
You need flexible check filtering (regex patterns, specific names, exclusions)
You're coordinating workflows triggered by repository_dispatch or external events
Consider native GitHub Actions features when
All your jobs are in the same workflow → use needs
You only work on the default branch and simple triggers suffice → use workflow_run
Quickstart
Workflow A - Runs tests
name: Test
on: [push]
jobs:
test:
name: Run tests
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm test
By default, if you use check-name or check-regexp and no checks match the filter, the action will fail with the message "The requested check was never run against this ref, exiting...".
If you want the action to succeed when no checks match the filter (useful for conditional workflows where certain checks only run on specific file changes), you can set fail-on-no-checks to false:
Wait for services that publish duplicate check names
Some services publish multiple check_runs under the same name on a single
commit — one per environment, retry, or internal worker. By default only the
most recent run for a given name is considered, so when these runs finish at
different times the first one to complete determines the reported status. A
single early failure can then fail the wait even though a later run of the same
name succeeds, making the result non-deterministic from one CI run to the next.
Set wait-for-duplicates: true to require every check sharing a name to
succeed before the action continues:
Pagination: The action handles up to 100 concurrent workflow runs. If you have more, some may not be detected.
API Rate Limits: Frequent polling may hit GitHub API rate limits. Increase wait-interval if needed.
Alternatives
Using needs
For jobs in the same workflow, use the native needs keyword:
jobs:
test:
runs-on: ubuntu-latest
steps:
- run: npm test
deploy:
needs: test # Waits for test to complete successfully
runs-on: ubuntu-latest
steps:
- run: npm run deploy
Using workflow_run
For triggering workflows on the default branch after another workflow completes:
There are sample workflows in the .github/workflows directory that demonstrate the action. The wait_omitting-check-name workflow waits for two simple tasks, while wait_using_check-name only waits for a specific task.
TopGit's last sync did not record any GitHub topics for lewagon/wait-on-check-action. GitHub topics appear in the right sidebar of a repository page; that's the authoritative place to check.
How active is development on lewagon/wait-on-check-action?
The most recent commit recorded on lewagon/wait-on-check-action was 7 days ago, based on the GitHub push timestamp. The repository has 76 forks — one of the better signals of community interest.
How many stars does lewagon/wait-on-check-action have?
lewagon/wait-on-check-action has 395 GitHub stars — refresh the page for the live number, or check github.com/lewagon/wait-on-check-action. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What language is lewagon/wait-on-check-action written in?
lewagon/wait-on-check-action is written primarily in Ruby. GitHub's language field is based on the largest share of bytes in the default branch.
Where do I read more about lewagon/wait-on-check-action?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/lewagon/wait-on-check-action is the definitive source.
Read full README in the tab above.
Want a second opinion on wait-on-check-action?
Ask an AI that can read this page — one click and you get its take on wait-on-check-action.
/wait-on-check-action
