Incident response guides
Signals to check first, command examples, common misdiagnoses, and recovery order. After reading, practice on a problem about the same failure.
When GitHub Actions succeeds but only the rollout failsAn InfraTree guide that lays out the first signals to check, the CLI verification order, common misdiagnoses, and a safe recovery path when the build logs look fine but the failure surfaces only on the target deploy cluster or runtime.CI/CD3 min readWhen the CI cache restores the wrong dependency graphAn InfraTree guide that lays out the first signals to check, the CLI verification order, common misdiagnoses, and a safe recovery path when package.json, the lockfile, and artifacts no longer agree even after a cache hit.CI/CD3 min readWhen a self-hosted runner job stays stuck in queuedAn InfraTree guide that lays out the first signals to check, the CLI verification order, common misdiagnoses, and a safe recovery path when the runner appears registered but can't pick up jobs because of label, group, network, or token issues.CI/CD3 min readThe checking order when GitHub Actions succeeds but only the deploy failsAn InfraTree guide that lays out the first signals to check, the CLI verification order, common misdiagnoses, and a safe recovery path when the workflow is green but the failure happens only in the rollout, promotion, or health check stage.CI/CD3 min readWhen Preview passes but the secret is missing only under the production feature flagA guide to splitting secret scope and environment contract first when the preview environment is healthy but the secret path looks empty only the moment you turn on a production flag or release toggle.CI/CD3 min read