Production-ready GitHub Actions workflows for CI/CD. Self-contained, configurable, and designed for both public and private repositories.
- Choose workflow from Available Workflows
- Copy manifest example to
.github/workflows/{name}.ymlin your repository - Modify pipeline configuration to match your needs - see Docs for all options, required permissions, and supported triggers
- Ensure secrets/vars are configured - follow setup instructions in Docs
- Push and run - enjoy!
💡 Pro Tip: Start from the examples in examples/ and tailor inputs/secrets using the docs.
| Workflow | Description | Docs | Example |
|---|---|---|---|
| docker-ops | Build, scan, and publish Docker images to multiple registries (Docker Hub, GCP, ACR) with security scanning and SBOM | 📖 Docs | 📋 Example |
| npm-release-ops | Build and publish npm packages with provenance, versioning, and release automation | 📖 Docs | 📋 Example |
| wp-gh-release-ops | Generate and publish WordPress plugin releases on GitHub | 📖 Docs | 📋 Example |
- Reusable - Designed for
workflow_callconsumption - Self-contained - No internal or proprietary dependencies
- Configurable - Explicit inputs and secrets
- Documented - Complete setup guides and examples
- AI-friendly - Structured metadata for LLM parsing
Each template is structured as follows:
- Workflow file (
.github/workflows/) - Template definition with inputs/secrets - Documentation (
docs/) - Setup guides, configuration options, troubleshooting - Examples (
examples/) - Real-world usage patterns with variable/secret patterns
To add a new reusable workflow:
- Create your workflow in
.github/workflows/. - Add a setup guide in
docs/and an usage example inexamples/. - Ensure your workflow inputs follow the standard registry-prefix naming convention in descriptions (e.g.,
Docker Hub: Image Name).
Infrastructure workflows (tests, release automation, etc.) are marked with a _ prefix and are intended for internal use only.
MIT License - see LICENSE