/explore
|
You are here 
|
localheinz.com | ||
| | | | |
tech.michaelaltfield.net
How to detect malicious bidirectional unicode characters in PR commits using a GitHub Actions workflow (Defending against Trojan Source attacks) |
|
| | | | | ||
| | | | |
davquar.it
A GitHub Action is the automatic execution of a job, after a specified trigger on a GitHub repository. For example, let's say that we want to run a linter on each new commit, we can create a GitHub action to do it. In this post we'll see a workflow to automatically deploy a Hugo site on GitHub Pages. |
|
| | | | | ||
| | | | |
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. |
|
| | | |||
