Explore >> Select a destination
|
You are here 
|
cookie.engineer | ||
| | | | |
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. | |
| | | | |
www.architect.io
|
|
| | | | | Learn how to automate the steps to build, test, and deploy your code using GitHub Actions. | |
| | | | |
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. | |
| | | | |
dotnet.github.io
|
|
| | | |||
