Architecting Secure GitHub Actions Self-Hosted Runners
Learn how to architect GitHub Actions self-hosted runners using ephemeral mode and network segmentation to balance internal access with build isolation.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to architect GitHub Actions self-hosted runners using ephemeral mode and network segmentation to balance internal access with build isolation.
Swap static cloud access keys in GitHub Actions for short-lived OIDC tokens, with constraints, an AWS trust-policy example, and validation steps.
Learn how to tune Qodana inspections with a custom .qodana.yml file and publish an HTML report to the Qodana dashboard from a GitHub Actions workflow.
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.
Rapid PR pushes spawn stale CI runs that waste minutes and confuse required checks. Learn how to scope GitHub Actions concurrency groups to cancel superseded pull_request runs while leaving push and deploy workflows untouched.