Explore >> Select a destination
|
You are here 
|
janik6n.net | ||
| | | | |
blog.jpalardy.com
|
|
| | | | | Jonathan Palardy's blog about technology | |
| | | | |
kinoshita.eti.br
|
|
| | | | | Normally when you add test coverage to a GitHub repository, the reporting part boils down to a simple call to some API that will post to a third-party external service like Coveralls or Codecov. Many are already on the GitHub Actions Market Place and a few lines of YAML are enough. A Codecov coverage report We had to report the test coverage of a private GitHub repository of a project I am working on at the moment, that could not have integration with other services besides GitHub. | |
| | | | |
navendu.me
|
|
| | | | | An exploration of continuous delivery workflows for building and managing APIs at scale. | |
| | | | |
lea.codes
|
|
| | | Sprinkle your JavaScript codebase with type annotations in JSDoc, run checks against it and auto-generate documentation. | ||
