{"repo":"we-cli/coverage-badge-action","free":true,"listed":false,"github":"https://github.com/we-cli/coverage-badge-action","clone":"git clone https://github.com/we-cli/coverage-badge-action.git","description":"Create a coverage badge via GitHub Actions","language":"JavaScript","stars":61,"topics":["coverage","github-actions","ci","testing"],"license":"MIT","category":"dev-tools","readme_excerpt":"coverage-badge-action   Similar Projects - https://github.com/jaywcjlove/coverage-badges-cli - https://github.com/GaelGirodon/ci-badges-action Difference - ✅ No gist-id required - ✅ No github-token required - ✅ No entire upload to gh-pages - ✅ Just patch and push to gh-pages - ✅ Supports Node.js & pytest Todolist - [ ] avoid redandunt diff from equivalent svgs - [x] auto create deploy branch - [x] support gh-pages-debug for non-defuault branches - [x] fix case of concurrent jobs to deploy gh-pages Update: supports pytest Usage 1. Make sure you have gh-pages branch and have GitHub Pages on: See Step.6 in 🚀 Blog Setup via Github Fork 6\\. (Important) Select both gh-pages and / (root) in Project Settings - Pages 1. Give workflow permission: On your repository Settings - Action - General - Workflow permissions choose Read and Write permissions 2. Whatever the coverage tool is, don't forget to have reporter=json-summary enabled: 3. Add the action to your current workflow 4. Add the badge to your README.md Replace the and above, like: and you get:","default_branch":null,"files":null,"tree":[],"storefront":"/r/we-cli","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/we-cli/coverage-badge-action/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}