Explore >> Select a destination
|
You are here 
|
code.dblock.org | ||
| | | | |
xvnpw.github.io
|
|
| | | | | Introducing the Fabric Agent Action - a GitHub Action that automates complex workflows using AI-powered agents and Fabric Patterns. | |
| | | | |
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. | |
| | | | |
securitylab.github.com
|
|
| | | | | In this article, well discuss some common security malpractices for GitHub Actions and workflows, and how to best avoid them. Our examples are based on real-world GitHub workflow implementation vulnerabilities the GitHub Security Lab has reported to maintainers. | |
| | | | |
dotnet.github.io
|
|
| | | |||
