github-actions-templates

Use a test workflow triggered on push and pull_request events with a matrix strategy for Node versions like 18.x and 20.x. Steps include actions/checkout, actions/setup-node with npm caching, npm ci, linting, and running tests with optional Codecov coverage upload.

Use docker/login-action to authenticate to a registry like ghcr.io, docker/metadata-action to generate tags from branches and semver, and docker/build-push-action with GitHub Actions cache. Grant packages:write permission and use the built-in GITHUB_TOKEN secret.

Yes, configure cloud credentials with aws-actions/configure-aws-credentials, update kubeconfig via aws eks update-kubeconfig, then run kubectl apply and kubectl rollout status. Add a verification step with kubectl get pods to confirm the deployment.

Add Trivy filesystem scanning via aquasecurity/trivy-action and upload SARIF results to GitHub Security with codeql-action/upload-sarif. You can also run Snyk scans using snyk/actions with a SNYK_TOKEN secret.

Reusable workflows are defined with the workflow_call trigger and accept typed inputs and secrets. Other workflows invoke them with the uses keyword, passing parameters like node-version, which standardizes common pipeline logic across repositories.

Avoid them when your task involves a different CI platform like GitLab CI, or when you need environment-specific validation beyond template scope. Always review secrets handling, permissions, and approval gates against your organization's security requirements before deploying.