CLI trigger for checkly.
...
steps:
- name: Checkly Trigger
uses: tj-actions/checkly-trigger@v1
with:
trigger-url: ${{ secrets.TRIGGER_URL }}| INPUT | TYPE | REQUIRED | DEFAULT | DESCRIPTION |
|---|---|---|---|---|
| deployment | string | false | "false" |
Set to true to record each trigger invocation as a deployment event. |
| deployment-id | string | false | The deployment id of your triggered check, i.e. "deployment-1". |
|
| environment-name | string | false | The environment name of your triggered check, i.e. "production". |
|
| environment-url | string | false | A staging or preview URL injected as ENVIRONMENT_URL in browser checks and auto-replaced in API checks. |
|
| repository | string | false | "${{ github.repository }}" |
Repository name, i.e. "checkly/backend-api". |
| run-location | string | false | "us-east-1" |
An optional data center location where to run your triggered check. Use the shorter names here, like eu-west-1 or us-west-1. |
| sha | string | false | "${{ github.sha }}" |
Git hash, tag, version "v1.0.1" or other identifier making this deploy unique. |
| trigger-url | string | true | The URL of the Checkly trigger. |
- Free software: MIT license
If you feel generous and want to show some extra appreciation:
This package was created with Cookiecutter using cookiecutter-action
Report bugs at https://github.com/tj-actions/checkly-trigger/issues.
If you are reporting a bug, please include:
- Your operating system name and version.
- Any details about your workflow that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.