GitHub workflow components for code repositories.
Important
Keep pipelines safe and DRY!
Tip
Rather than copying and pasting from one workflow to another, you can make workflows reusable.
Source: Reusing workflow configurations
Containers:
.NET:
Git:
GitHub Pages:
Helm:
Markup (Markdown, YAML, shell scripts):
Node.js:
Terraform:
Tip
Composite actions allow you to collect a series of workflow job steps into a single action which you can then run as a single job step in multiple workflows. Source: Creating a composite action
Containers:
- Build and push an image for one or more platforms
- Sign an image with Cosign
- Setup QEMU to build images for other platforms
- Scan an image or a directory with Trivy
- Setup Trivy
.NET:
- Build, test the code and analyze it with Sonar
- Build and test the code
- Install the SDK, lint the code and restore NuGet packages
- Package the projects and push them to a NuGet registry
Git:
Go:
Helm:
- Setup Helm
- Setup chart-releaser
- Setup chart-testing
- Setup helm-repo-html
- Setup helm-unittest
- Setup kube-linter
- Setup kubeconform
Kubernetes:
License compliance:
MongoDB:
Node.js:
Search engines:
Code scanning:
Sonar:
SBOM:
Task:
Terraform:
Note
These composite actions download official release binaries directly (with SHA256 checksum verification) instead of relying on third-party marketplace actions, reducing supply-chain exposure.
Linux runners only (for example ubuntu-latest).