ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #githubactions
Learn how to architect GitHub Actions self-hosted runners using ephemeral mode and network segmentation to balance internal access with build isolation.
Reusable workflows let you define CI once and call it from multiple repositories. Learn how to structure them, version them safely, and avoid the common pitfalls that break shared pipelines.
Learn how to define and call GitHub Actions reusable workflows to share CI/CD steps across repositories, with a concrete example, limits, and pitfalls to avoid.
Multiple quick pushes can trigger redundant GitHub Actions workflows. Learn how concurrency groups with cancel-in-progress reduce CI waste, the trade-offs of aggressive cancellation, and how to configure it safely.
Compare GitHub-hosted and self-hosted runners across cost, security, performance, and maintenance, with a validation checklist and workflow example.
Build a gated production deploy pipeline using a caller workflow, a reusable deployment workflow pinned to a commit SHA, and a protected environment with required reviewers.
Centralize CI/CD steps with GitHub Actions reusable workflows. Pin commits, map inputs and secrets, and isolate trust boundaries to reduce duplication and protect secrets. Practical checks and failure‑mode mitigations included.
Stop duplicating YAML across your repositories. Learn how to use GitHub Actions reusable workflows to centralize CI/CD logic, enforce standards, and manage versions safely.
Replace long‑lived cloud credentials in GitHub Actions with a short‑lived OIDC token. Minimal design, claim‑based trust, operational checks, and failure modes explained for AWS, GCP, and Azure.
yaml