Deployments & CI/CD
Automated builds, tests and releases — reproducible in CI/CD pipelines.
GitHub Actions
CI/CD for builds, tests and deployments.
Services
Integrations & workflows
Connect systems and automate processes (e.g. n8n, webhooks).
Monitoring & security
Observability, backups, hardening and predictable operations.
GitHub Actions is my default choice for CI/CD when code quality, reproducible builds and automated deployments matter. Workflows live in the repo, remain transparent and scale from small sites to complex pipelines.
What I typically automate
In practice I set up lint/typecheck, build jobs, link checks, preview deployments and release automation. With smart caching (npm, build artefacts) pipelines stay fast, and environments (staging/production) remain cleanly separated.
Security & deployments
Secrets belong in GitHub Environments, not in code. For cloud deployments I prefer OIDC over long‑lived access keys. Branch protection, code owners and required checks make releases predictable and safer.
GitHub Actions reduces manual steps and “works on my machine” issues—while speeding up iteration through consistent quality gates.