step-security/Dispatch Workflow
A GitHub action to dispatch a remote GitHub workflow and optionally retrieve its information
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| dispatch-method | The method that will be used for dispatching GitHub workflows: repository_dispatch, workflow_dispatch. | yes | — |
| repo | Repository of the workflow to dispatch. | yes | — |
| owner | Owner of the given repository. | yes | — |
| token | GitHub API token for making API requests. | yes | — |
| ref | 'If the selected dispatch method is workflow_dispatch, the git reference for the workflow. The reference can be a branch or tag name.' | no | — |
| workflow | If the selected dispatch method is workflow_dispatch, the ID or the workflow file name to dispatch. | no | — |
| event-type | If the selected dispatch method is repository_dispatch, what event type will be triggered in the repository. | no | — |
| workflow-inputs | A JSON object that contains extra information that will be provided to the dispatch call. | no | {} |
| discover | A flag to enable the discovery of the Run ID from the dispatched workflow. | no | false |
| starting-delay-ms | The delay, in milliseconds, before executing the function for the first time. | no | 200 |
| max-attempts | The maximum number of times to attempt read-only GitHub API requests. | no | 5 |
| time-multiple | The starting-delay-ms is multiplied by the time-multiple to increase the delay between reattempts. | no | 2 |
Outputs
no outputs