-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add README documenting main parts of project
- Loading branch information
1 parent
a503c87
commit 5b5fc1f
Showing
1 changed file
with
29 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
# GitHub Actions Experiment | ||
|
||
The main workflow to pay attention to is the one that runs | ||
canaries/healthchecks using Playwright (`.github/workflows/playwright.yml`). | ||
|
||
This workflow can be dispatched manually from the GitHub Actions UI or via a | ||
script located in the bin directory: | ||
|
||
```bash | ||
$ ./bin/send-workflow-dispatch.sh | ||
``` | ||
|
||
In order to run that shell script dispatch, you need to have a personal GitHub | ||
access token created and set in the `.env.local` file. To do that, start by | ||
copying the example environment file. | ||
|
||
```bash | ||
$ cp .env.local{.example,} | ||
``` | ||
|
||
The `playwright.yml` workflow will kick off several other workflows that run | ||
playwright canaries/healthchecks against several web properites. The specific | ||
playwright logic for each of those canaries lives in `src/canaries`. | ||
|
||
Each of those Playwright canaries can be individually, locally invoked like so: | ||
|
||
```bash | ||
$ npm run healthcheck -- src/canaries/playwright-total-typescript.ts | ||
``` |