Coverage Badge
ActionsTags
(2)
- ✅ No gist-id required
- ✅ No github-token required
- ✅ No entire upload to gh-pages
- ✅ Just patch and push to gh-pages
-
Make sure you have gh-pages branch and have GitHub Pages on:
# if you don't have gh-pages yet git switch --orphan gh-pages git commit --allow-empty -m "Initial commit" git push -u origin gh-pages
See Step.6 in 🚀 Blog Setup via Github Fork
6. (Important) Select both gh-pages and / (root) in Project Settings -> Pages
-
Whatever the coverage tool is, don't forget to have
reporter=json-summaryenabled:// package.json - "test:cov": "c8 xv", + "test:cov": "c8 -r text -r json-summary xv", // or - "coverage": "nyc mocha", + "coverage": "nyc -r text -r json-summary mocha",
-
Add the action to your current workflow
# .github/workflows/test.yml name: Test on: [push, pull_request, workflow_dispatch] jobs: test: runs-on: ubuntu-latest steps: # Your original steps - uses: actions/checkout@v3 - uses: actions/setup-node@v3 - name: Install run: npm install - name: Test and Coverage run: npm run test:cov # or npm run coverage # Add this - name: Update Coverage Badge uses: we-cli/coverage-badge-action@main
-
Add the badge to your README.md
<!-- README.md --> + [](https://github.com/<you>/<repo>/actions)Replace the
<you>and<repo>above, like:<!-- README.md --> + [](https://github.com/we-cli/jayin/actions)and you get:
Coverage Badge is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.
Tags
(2)Coverage Badge is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.