Repository files navigation

These workflow examples comprise three parts:

• .github/workflows/reusable-*.yaml - Designed to be reusable as a "called" workflow, and has aworkflow_call event in it. They would exist in a central repository and called by other repositories. The central repository needs to bepublic,internal, orprivate and enabled for GitHub Actions sharing in repository Settings.
• templates/call-*.yaml - these are the "calling" templates that you would copy to all your code and IaC repositories. Each of their jobs has the specialuses: <github-path> to point to the reusable workflow.
• .github/workflows/call-local*.yaml - For testing. Calls a local workflow in the same directory. ProTip: Make tests for your reusable workflows! Either in the same repository as this one shows, or from a separate repository full of tests. You'll thank me later.

⚠️DO NOT call this workflow directly, rather, use it as a template repository and fork it for your own reusable workflow. I might change this workflow at anytime, based on new GHA features or learnings, and your calling workflow might break.⚠️

• .github/dependabot.yml will make PRs for version updates to your Actionsand Dockerfiles.
• .github/linters/ stores linter configs used by Super-Linter. ProTip: symlink these to the preferred location to use the same linters locally.
• templates/call-super-linter.yaml is a workflow that calls Super-Linter, which I'm storing the full reusable workflow inbretfisher/super-linter-workflow.
• templates/call-docker-build.yaml is a workflow that calls a Docker build (awesomesauce!), which I'm storing the full reusable workflow inbretfisher/docker-build-workflow.
• templates/call-docker-build-promotion.yaml is an advanced workflow that calls a build workflow on PR, and then on merge it will call that workflow with different values andalso creates a GitOps-style PR to deploy the new image to a Kubernetes cluster.
• templates/call-snyk-scan-image.yaml is a workflow that calls aSnyk scanin this repository.
• templates/call-trivy-scan-image.yaml is a workflow that calls a reusableTrivy scanin this repository.

• (you are here)bretfisher/github-actions-templates - Main reusable templates repository
• bretfisher/super-linter-workflow - Reusable linter workflow
• bretfisher/docker-build-workflow- Reusable docker build workflow
• bretfisher/docker-ci-automation - Step-by-step video and example of a Docker CI workflow
• My full list of container examples and tools

• Docker Build/Push Action advanced examples
• My full list of container examples and tools

• My Cloud Native DevOps Discord server
• My weekly YouTube Live show
• My weekly newsletter
• My courses and coupons