FFerhat Yildiz8h ago · 26 min readDeploying Terraform to AWS with GitHub Actions and OIDCAs applications grow, teams need to create and change infrastructure more often. Repeating those changes by hand takes time and makes it easy to miss a setting or configure environments differently. T1Rblog.turingts.com
SsoftverseAdmin41m ago · 13 min readCI/CD for Monorepos 2026: Build Only What ChangedTL;DR: A monorepo with naive CI rebuilds the world on every commit, so pipelines get slower exactly as the repo succeeds. The fix is affected-only delivery: detect what changed, expand through the depdevopsenginer.hashnode.dev
SsoftverseAdmin2h ago · 9 min readGitHub Actions Reusable Workflows & Composite Actions (2026): Stop Copy-Pasting YAML Across ReposTL;DR Copy-pasted workflow YAML is a maintenance debt with a blast radius: fix a bug in one repo's CI and the other nine quietly keep the bug. Reusable workflows (on: workflow_call) share whole jobs devopsenginer.hashnode.dev
FFelipe Maschio13h ago · 7 min readHow I got a thread dump from a timed-out GitHub Actions testA test hangs in CI, the job sits there for 30 minutes, and GitHub Actions cancels it. The log says the job exceeded its time limit and nothing about what the test was doing when it got stuck. Running maschiojv.hashnode.dev
OOnlive Server20h ago · 9 min readAutomating Pull-Request Preview Environments: Dynamic Subdomains with Traefik on a Development VPSTesting new application features directly on a live website can create unnecessary risks. A small change in the frontend, API, or database integration may affect existing functionality. Developers nee1onliveinfotech.hashnode.dev
AAdithya M S19h ago · 10 min readGitHub Actions for Beginners: Understanding Triggers, Conditions, Variables and Debugging Your WorkflowsIs your pipeline running only when it should? In Part 1 we built a pipeline that lints, tests, and builds on every push. That’s a good start, but a pipeline that runs on everything isn’t really requiradithyameda.hashnode.dev
DDemoVexa1d ago · 6 min readA Nightly CI Job for Demo Video Renders: Queueing, Retries and ArtifactsA nightly render job is a scheduled CI workflow that rebuilds your product demo videos from the latest code while nobody is waiting on it, then stores the files somewhere your team can grab them in thdemovexa.hashnode.dev
AAI Developer3d ago · 23 min readEvals in CI: A Zero-Regression Merge Gate for LLM Features with pytest and GitHub ActionsA teammate changes one line in a prompt. They want the support-ticket summaries to sound a bit warmer. They try three tickets in the playground, the output looks better, and the PR gets merged with a aidevpro.hashnode.dev
WWaqas Shahid3d ago · 2 min readGitHub Actions Explained: Automation That Runs on Every PushIntroduction Tests only help if they actually run. GitHub Actions is the automation built into GitHub: every time you push code or open a pull request, it can run your Jest tests, your Cypress suite, practicaldevblog.hashnode.dev
SShipKit4d ago · 5 min readWhy Docker layers don't stay cached in GitHub Actions (and how type=gha works)Your Docker build works in GitHub Actions, but the dependency install step runs from scratch on each push. Here's how the GitHub Actions cache for Docker layers works with Buildx and docker/build-pushshipkit.hashnode.dev