time-loop/Trigger Workflow and Wait
This action triggers a workflow in another repository and waits for the result.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| owner | The owner of the repository where the workflow is contained. | yes | — |
| repo | The repository where the workflow is contained. | yes | — |
| github_token | The Github access token with access to the repository. It is recommended you put this token under secrets. | yes | — |
| github_user | The name of the github user whose access token is being used to trigger the workflow. | no | — |
| ref | The reference of the workflow run. The reference can be a branch, tag, or a commit SHA. Default: main | no | — |
| run_name | The name of the run to filter by when checking for workflows. This is helpful when dispatching workflows from matrix calls | no | — |
| wait_interval | The number of seconds delay between checking for result of run. | no | — |
| workflow_file_name | The reference point. For example, you could use main.yml. | yes | — |
| client_payload | Payload to pass to the workflow, must be a JSON string | no | — |
| propagate_failure | Fail current job if downstream job fails. default: true | no | — |
| trigger_workflow | Trigger the specified workflow. default: true | no | — |
| wait_workflow | Wait for workflow to finish. default: true | no | — |
| comment_downstream_url | Comment API link for commenting the downstream job URL | no | "" |
| comment_github_token | The Github access token with access to the repository for comment URL. It is recommended you put this token under secrets. | no | ${{ github.token }} |
Outputs
| name | description |
|---|---|
| workflow_id | The ID of the workflow that was triggered by this action |
| workflow_url | The URL of the workflow that was triggered by this action |
| conclusion | Conclusion of the job, i.e pass/failure |