Skip to content

Commit

Permalink
readme [skip ci]
Browse files Browse the repository at this point in the history
  • Loading branch information
donaldoakes committed Feb 17, 2023
1 parent 3fcfc01 commit b1957f5
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ jobs:
with:
node-version: '16.x'
- run: npm install
- uses: ply-ct/ply-action@v2.4
- uses: ply-ct/ply-action@v2.5
```
This example runs all Ply tests and fails if they don't succeed.
Expand All @@ -44,7 +44,7 @@ able to retrieve their workflow build status. The question mark at the end of th
## Private repositories
Private repositories can use ply-action as in the example above, but to include a badge some additional configuration is needed:
```yaml
- uses: ply-ct/ply-action@v2.4
- uses: ply-ct/ply-action@v2.5
with:
github-token: ${{ secrets.MY_GITHUB_TOKEN }}
badge-branch: badge
Expand All @@ -62,7 +62,7 @@ If you've already integrated Ply CLI commands into a GitHub workflow (say with c
skip Ply test execution altogether, and use ply-action simply to perform a badge commit based on the results of previous Ply CLI run.
In that case, specify the path to an overall Ply results file created using the `--resultFile` [CLI arg](https://ply-ct.org/ply/topics/config):
```yaml
- uses: ply-ct/ply-action@v2.4
- uses: ply-ct/ply-action@v2.5
with:
ply-path: node_modules/ply-ct/dist
result-file: test/api/results/actual/ply-results.json
Expand Down

0 comments on commit b1957f5

Please sign in to comment.