CI Workflow Pack

Fifteen GitHub Actions workflows you can copy, paste and understand. Every file starts with a header that says what to set and why each non-obvious line exists.

$19Buy the CI Workflow PackOne-time payment, instant download.

This is a product of Passing Build, the site you are reading. Buying it supports the site; it is not an affiliate link.

What is inside

FileWhat you get
01Node CI. npm cache, a Node version matrix and lint/test/build, with the concurrency and permissions settings that keep runs cheap and safe.
02Python CI. pip cache keyed on your requirement files, a version matrix, pytest with coverage and test reports as artifacts.
03Docker to GHCR. Build and push with buildx, GitHub cache for layers and metadata-action tags for branches, PRs, semver and SHA.
04Multi-platform Docker. One tag for linux/amd64 and linux/arm64 through QEMU, with provenance and SBOM attached.
05Deploy to AWS (OIDC). ECR plus ECS, or S3 plus CloudFront, with no stored access keys and notes on the trust and least-privilege policies.
06Deploy to Cloud Run. Workload Identity Federation and Artifact Registry instead of a service-account key, with the one-time gcloud setup included.
07Deploy to Azure Web App. Federated credentials tied to one environment, with build and deploy split into separate jobs.
08Terraform. Plan posted as a PR comment, the saved plan applied on main only after an environment approval.
09Release on tag. Cross-platform build matrix, SHA-256 checksums and a GitHub Release with generated notes.
10Monorepo path filters. Run only the jobs whose folders changed, plus one always-running required check so merges never hang on a pending check.
11Reusable workflow + caller. workflow_call with typed inputs, an optional secret and outputs, and a caller that fans out over a matrix.
12Scheduled job. UTC cron done right: off-peak minute, no overlap, timeout, and a failure issue or chat alert you will actually see.
13Security scanning. Dependency review on pull requests and CodeQL per language on push, PRs and weekly.
14Cost-saving baseline. A skeleton that stops minute leaks: concurrency cancel, paths-ignore, draft skip, timeouts and artifact retention.
15Self-hosted runner. Custom labels, a fork guard and workspace cleanup before and after, with the security caveats up front.

Also included: validar.py (a checker), versions.json (the action versions the pack was verified against) and actionlint.yaml. Every workflow has an explicit minimalpermissions: block, timeout-minutes on every job and, where it matters, aconcurrency group.

Who it is for

  • Developers and small teams who want a working CI/CD starting point without reading 40 pages of docs.
  • Freelancers and consultants who set up pipelines for clients (the license allows it).
  • People who already have pipelines and want a reference for OIDC deploys, monorepo checks or cost control.

It is not for you if you want a managed service, a fully custom pipeline written for your stack, or workflows for CI systems other than GitHub Actions.

What "validated" means, and what it does not

Each workflow passes actionlint and uses the current major version of its actions. That catches syntax errors, wrong expression types, unknown action inputs and common shell and permissions mistakes. It does not prove the workflow works in your repository.

The deploy workflows (AWS, Cloud Run, Azure, Terraform) have not been executed against real cloud accounts by us. Treat them as carefully commented, linted starting points, and try them in a non-production environment first.

License summary

  • Use the workflows in your own projects and your clients' projects, public or private, commercial or not.
  • Modify and combine them freely; no attribution required.
  • Do not resell, share or publish the pack itself, for example as a public template repository.
  • Provided as is, without warranty. The full license is in LICENSE.txt in the download.

Price

$19, one time. No subscription.

FAQ

What does "validated" mean here?

Every workflow passes actionlint (syntax, expression types, the action inputs it knows about, plus shell and permissions checks) and uses the current major version of each action as of the date in the README. The deploy workflows (AWS, Cloud Run, Azure, Terraform) have not been run against live cloud accounts by us, because they depend on your account, roles and resources. Test them in a non-production environment first.

Do I need to know GitHub Actions already?

Basic familiarity helps, but each file opens with a comment block listing what to set and why each non-obvious line exists, so you can learn the pattern while you adapt it. You replace the example commands (npm test, pytest, the Go build) with your own.

Can I use the workflows for clients or at work?

Yes. You can use and modify them in your own projects and in projects you build or maintain for clients, in public or private repositories, on any number of your repositories. You may not resell, redistribute or publish the pack itself, including as a public template repository. The full text is in LICENSE.txt inside the download.

Will the action versions go out of date?

Eventually, yes. Third-party actions move on. The pack includes versions.json and a validar.py script that checks every workflow with actionlint and, with the --online flag, compares the pinned versions with the latest tags on GitHub. You can run it whenever you like. We do not promise a fixed update schedule.

Is there a free sample, and what about refunds?

A free sample with three of the workflows (Node CI, Docker to GHCR and the cost-saving baseline) is planned as a public GitHub repository; it will be linked here when it is live. Refunds follow the policy of the store that sells the pack and are shown at checkout.