Explore >> Select a destination
|
You are here 
|
localheinz.com | ||
| | | | |
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. | |
| | | | |
simonwillison.net
|
|
| | | | | I figured out a GitHub Actions pattern to keep track of a file published somewhere on the internet and automatically open a new repository issue any time the contents of ... | |
| | | | |
tech.michaelaltfield.net
|
|
| | | | | How to detect malicious bidirectional unicode characters in PR commits using a GitHub Actions workflow (Defending against Trojan Source attacks) | |
| | | | |
www.augmentedmind.de
|
|
| | | Improve the build speed of Docker images in CI pipelines, using BuildKit caching tricks, the .dockerignore file and package managers tweaks. | ||
