Coverage updates
See original GitHub issue- I’m not seeing updated coverage numbers in PRs. I think the reason is that coveralls only runs on
master
, and not for PR builds. Does it make sense to change that? - Given #1297 we should probably start measuring coverage on the
beta
branch. I don’t see a big advantage to measuring onmaster
. Should we transition over the config and the badge on the master readme from one to the other? Alternatively we could keep both badges. I’m not sure the native Coveralls badge lets you override the label on the second badge, but the one in Shields will.
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (11 by maintainers)
Top Results From Across the Web
Change or update your Marketplace Health Coverage
Find out how to change or update your current health coverage for 2023. Learn about Marketplace health insurance plans at Healthcare.gov.
Read more >MassHealth Coverage Updates - Mass.gov
Updates and notification information for MassHealth members. ... For MassHealth members with Medicare: resources for your prescription drug coverage.
Read more >Coronavirus (COVID-19) Updates | Blue Cross Blue Shield
Looking for COVID-19 coverage and benefit information? Find your BCBS company. Providing Support During the COVID-19 Pandemic.
Read more >Coverage updates - Regence
Coverage updates. A National Coverage Determination (NCD) is a federal mandate of what Medicare covers. View the full NCD summary for each topic...
Read more >2023 Projected Health Insurance Exchange Coverage Maps
Current snapshot: Insurer Participation in Health Insurance Exchanges (PDF) ... Updates. March 5, 2020 Information Related to COVID–19 Individual and Small ...
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 Free
Top 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
The reason for that is no more. It was tricky to make that work with Greenkeeper in the past, but that has been resolved, we can commit package-lock.json now
I’ve changed the default branch to “beta” 😃 I don’t think there is a need to change anything in coveralls, just all the badges should point to the beta branch, and maybe we could add two npm badges, one showing the “@latest” and one the “@beta” release?