github-actions-templates

Define a workflow triggered on push and pull_request, use actions/setup-node with a matrix of Node versions, cache npm dependencies, then run npm ci, lint, and test steps. Coverage results can be uploaded with codecov/codecov-action.

Use docker/login-action to authenticate to a registry like ghcr.io, docker/metadata-action to generate tags from branches and semver tags, and docker/build-push-action with GitHub Actions cache for layer caching.

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

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 to avoid duplicating pipeline logic.

Pinning actions to major versions like @v4 instead of @latest prevents unexpected breaking changes and reduces supply-chain risk. It ensures workflow behavior stays consistent across runs and repositories.

Attach an environment with required reviewers to the deployment job in the workflow YAML. GitHub pauses the run until a reviewer approves, and the job can also expose the deployment URL for traceability.