-
Should we add them? Presumably to the individual package's README file, where they would also show up in pub.dev.
```
[codecov](https://codecov.io/gh/aboutyou/dart_packages/branch/master/graph/bad…
-
I'm trying to use Codecov on Travis without using the key as you told me it can be done without and so in the name of efficiency I want to learn how it's done!
My .travis.yml and package.json look li…
Cleop updated
5 years ago
-
We should add coverage badges to all open source repos using either https://coveralls.io or https://codecov.io/
-
**Describe the problem/challenge you have**
**Describe the solution you'd like**
**Anything else you would like to add:**
**Environment:**
- Velero version (use `velero version…
-
Hey, what do you think about adding
* pypi version
* license (?)
* travis
* codecov
* readthedocs
badges to the readme?
kmike updated
7 years ago
-
1. Add code coverage analysis, for example: `go test -v -race -coverprofile="coverage.txt" -covermode=atomic ./...`
2. Add reporting to service like [Codecov](https://codecov.io/) or [Coveralls](http…
-
### Thanks for dropping by! 👋
We've recently released a whole new area of the app focused on flags. If you're not seeing it yet, keep your eyes peeled as we're slowly rolling it out to our users.
…
-
Orion should guarantee 90% or more of code coverage before being ready for production
The following badge must be included in README.md
[![codecov](https://codecov.io/gh/wesovilabs/orion/branch/…
-
And please also add badges into README Including :
- CI codecov
- GitHub release
- Docker Pulls
- Go Report
- TODOs
- gitter
- license
- etc..
refer to the kubevela repo for details.
-
## Brief summary of issue
When running yum info on this package it prints all what's in the README.md including special characters used for markdown, which is very inconvenient
### Types of issu…