Why?
Workflows run on every commit asynchronously, this is fine for most cases, however, you might want to wait for a previous commit workflow to finish before running another one, some example use-cases:
- Deployment workflows
- Terraform workflows
- Database Migrations
jobs:
xyz:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: durable-code/workflow-queue
with:
run-id: ${{ github.run_id }}
# only runs additional steps if there is no other instance of `my-workflow.yml` currently running| input | required | default | description |
|---|---|---|---|
github-token |
❌ | github.token |
The GitHub token used to call the GitHub API |
run-id |
✅ | - | The ${{ github.run_id }} of the caller workflow |
timeout |
❌ | 600000 |
timeout before we stop trying (in milliseconds) |
delay |
❌ | 10000 |
delay between status checks (in milliseconds) |