Skip to content

docs: Fix example snippets to use with Github Actions #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 21, 2020
Merged

docs: Fix example snippets to use with Github Actions #29

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,7 @@ If you run your tests on [GitHub Actions](https://glebbahmutov.com/blog/trying-g

```yaml
- name: Set code coverage commit status 📫
run: npx set-gh-status
run: npx -p check-code-coverage set-gh-status
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
```
Expand All @@ -115,7 +115,7 @@ If there is a coverage badge in the README file, you can add 2nd status check. T

```yaml
- name: Ensure coverage has not dropped 📈
run: npx set-gh-status --check-against-readme
run: npx -p check-code-coverage set-gh-status --check-against-readme
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
```
Expand All @@ -128,7 +128,7 @@ When setting a status on a GitHub pull request, you need to use SHA of the merge

```yaml
- name: Ensure coverage has not dropped 📈
run: npx set-gh-status --check-against-readme
run: npx -p check-code-coverage set-gh-status --check-against-readme
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
GH_SHA: ${{ github.event.after }}
Expand Down