ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #githubactions
Learn how to diagnose and fix GitHub Actions jobs that stay in the 'Queued' state, focusing on runner label mismatches, concurrency bottlenecks, and offline self-hosted agents.
Stop duplicating your GitHub Actions jobs. Learn how to use Matrix Strategies to test across multiple OS and runtime versions efficiently using include, exclude, and fail-fast settings.
actions/cache speeds up GitHub Actions by restoring your package manager's download store between runs — but only if your key includes a lockfile hash.
I run a CI workflow that connects to a PostgreSQL database during integration tests. Occasionally the workflow fails with a connection pool exhaustion error, even though the number of parallel jobs is below the database's max pool size. The workflow executes on GitHub‑hosted Ubuntu runners, which are virtual machines in Azure with a shared network stack. I s
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
Runner Environment Reproducibility Challenge Teams using GitHub Actions often face decisions between GitHub-hosted runners and self-hosted runners for maintaining consistent development environments across CI/CD pipelines. The core tension lies in achieving environment reproducibility while balancing maintenance overhead and platform compatibility. GitHub-ho
Goal To determine whether the OIDC identity token that GitHub Actions supplies is automatically refreshed when a single job contains a long‑running step that exceeds the token’s nominal lifetime. Scenario A workflow obtains an OIDC token, exchanges it for AWS STS credentials, sleeps for 12 minutes, and then makes a second AWS API call. Constraints The token
Graceful cleanup during workflow cancellation GitHub Actions sends SIGTERM to the runner process when a workflow is cancelled—either manually or via concurrency.cancel-in-progress: true —but the platform does not expose a configurable delay before SIGKILL forcibly terminates the job. Steps that need to flush buffers, release distributed locks, or notify exte