Fix build badge & coverage scripts
See original GitHub issueWe should fix the badge in Readme with build status, because “build failed” can be confusing for users. It seems the coverage script is broken too. So it would be nice to fix this and make integration with Travis-ci.
- Create
release/dev
branch - Setup Travis service
- Setup Coveralls service
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:39 (17 by maintainers)
Top Results From Across the Web
GitHub - dwyl/repo-badges
Anything below 100% coverage means the module/library has potential bugs which are unknown to the authors/users. We avoid using modules with less than...
Read more >Adding code coverage badge to your project - YouTube
This video shows how to add and update code coverage badge to your README without using external service, just https://shields.io and ...
Read more >Coverage Badge with GitHub Actions - FINALLY!
This is the only documented way to get coverage badges with GitHub ... We do some shell script magic to grab the correct...
Read more >Badges - GitLab Docs
Examples for badges can be the pipeline status, test coverage, latest release, or ways to contact the project maintainers. Badges on Project information...
Read more >Display build status/test coverage badges for a Laravel project
Suppose we have a Laravel project that includes a specific instruction to display both build status and code coverage report as badges in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I fixed the badge link to *.org and made some changes to the README. So when we’ll be sure that coveralls badge is working fine we need to make a patch version for npm.
Wow, thanks a lot!💚 Of course we will discuss each release (merging dev to the master), even non breaking, since in any case the npm repo is under your control 😃 I aim to avoid any breaking changes and there seems to be no reason for this, so the only potential breaking changes could be here is bug fixes like #254 😃 So, currently my goal is:
I will notify you when the
dev
branch will be ready for review and release, of course, if you will have some time and inspiration for this 😃