See this repositories .github directory for examples on linters, workflows, and dependabot.
-
.github/dependabot.ymlwill make PRs for version updates to your workflow steps. -
.github/linters/stores linter configs used by Super-Linter. -
.github/workflows/call-super-linter.yamlis a workflow that calls Super-Linter, which I'm storing the full reusable workflow in bretfisher/super-linter-workflow. -
.github/workflows/call-docker-build.yamlis a workflow that calls a Docker build advanced workflow, which I'm storing the full reusable workflow in bretfisher/docker-build-workflow. -
.github/workflows/call-snyk-scan-image.yamlis a workflow that calls a Snyk scan image at.github/workflows/reusable-snyk-scan-image.yaml. -
.github/workflows/call-trivy-scan-image.yamlis a workflow that calls a Trivy scan image at.github/workflows/reusable-trivy-scan-image.yaml.
Some workflows are reusable or are calling other reusable workflows in other repositories.
I name workflows depending on how they are used:
reusable-*.yaml- the workflow is designed to be reusable as a "called" workflow, and have aworkflow_callevent in them. They would exist in a central repository that is eitherpublicorinternaland called by other repositories.call-*.yaml- this calls a reusable workflow that lives in other repositories or files withuses: <github-path>.- Any other workflows are just designed to run inside a repository directly.
- (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