github-actions-templates

Define a workflow triggered on push and pull_request, use actions/checkout and actions/setup-node with a matrix of Node versions, then run npm ci, lint, and test steps. Upload coverage with codecov/codecov-action for reporting.

Use docker/login-action to authenticate to a registry like GHCR, docker/metadata-action to generate tags from branches and semver, and docker/build-push-action with GitHub Actions cache for faster builds.

Yes, configure cloud credentials with actions like aws-actions/configure-aws-credentials, update kubeconfig for your cluster, then run kubectl apply and kubectl rollout status to deploy and verify workloads.

Reusable workflows are defined with the workflow_call trigger and accept typed inputs and secrets. Other workflows invoke them with the uses keyword, avoiding duplication of common CI logic across repositories.

Add a job using aquasecurity/trivy-action to scan the filesystem and upload SARIF results to GitHub Security via codeql-action, or run snyk/actions with a SNYK_TOKEN secret for dependency vulnerability checks.

GitHub Actions may not fit if your repositories are hosted on GitLab or Bitbucket, where GitLab CI or Bitbucket Pipelines integrate natively. Self-hosted runners are recommended for sensitive workloads requiring network isolation.