domains / families / devops / github-actions-templates

github-actions-templates

combined

Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates. Production-ready GitHub Actions workflow patterns for testing, building, and deploying applications.

When to use

Create efficient, secure GitHub Actions workflows for continuous integration and deployment across various tech stacks.
Automate testing and deployment
Build Docker images and push to registries
Deploy to Kubernetes clusters
Run security scans
Implement matrix builds for multiple environments
Implement testing, matrix builds, artifact preparation or an explicitly authorized deployment workflow for an existing repository.

When not to use

The task is unrelated to github actions templates
You need a different domain or tool outside this scope
This skill supplies patterns, not an installed deployment program. Repository policy, runner trust and environment settings must be inspected. Review every third-party action at its full commit SHA and treat logs and uploaded artifacts as…

Skill page

Conflict

The two copies overlap in purpose (GitHub Actions workflow templates) but disagree on the core procedure. The first copy is a catalog of ready-to-paste YAML patterns (test, Docker, K8s, matrix, reusable, security) with generic best practices. The second copy is a security-hardened procedure that forbids the first copy's style: it requires inspecting the repo, reading specific local resources, pinning actions to full commit SHAs, setting persist-credentials: false, adding timeouts, and explicitly warns against publishing untrusted artifacts or labeling placeholders as deployments. Crowning the first copy would hide the second's mandatory security constraints and verification steps; crowning the second would hide the first's concrete multi-stack templates. They must be combined.