GitHub
682 incident problems in GitHub environments.
Read first
When 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 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 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 read
Recommended problems
Reviewed problems first, then problems with detailed scenarios.
CICD-001Finding the real failure point in GitHub Actions build logsA training scenario for isolating the true cause from logs where npm dependency conflicts and cache traces are mixed together.ReviewedCI/CDIntermediate20 minFreeCICD-007Builds failingA scenario that narrows down the root cause, centered on realigning the cache key strategy and lockfile consistency, in the situation of builds failing because the cache key gets tangled after a Node version upgrade.ReviewedCI/CDBeginner16 minFreeCICD-009Deployment failingA scenario that narrows down the root cause, centered on checking the permission-policy difference by event type, in the situation of a deployment failing because the secret is empty only on tag releases.ReviewedCI/CDIntermediate21 minFreeCICD-021Build cache key mismatch after lockfile updateA pipeline stays green on one branch and fails on another because the dependency cache key no longer matches the lockfile layout.ReviewedCI/CDBeginner17 minFreeCICD-031GITHUB_TOKEN read-only default blocks release provenance uploadThe workflow can build and test successfully, but the release job fails when it tries to publish attestations or update release metadata with a narrower token scope.ReviewedCI/CDIntermediate21 minProCICD-038Publish workflow never startsA formatting or version-bump workflow commits successfully, but the downstream publish workflow never runs because the triggering push used the repository token.ReviewedCI/CDBeginner16 minFree
All problems (682)
Could not resolve host: external API calls fail on one server onlyCould not resolve host: external API calls fail on one server only is a hands-on troubleshooting drill. Tell a DNS failure from a connectivity or remote outage. GitHub dns-resolution needs to be checked by narrowing scope, recent change, and the current live signal before roll...ReviewedNetworkBeginner3 minFreeSelf-hosted runner: No space left on device in the middle of buildsSelf-hosted runner: No space left on device in the middle of builds is a hands-on troubleshooting drill. Find what fills a long-lived runner's disk. GitHub Runner Hygiene needs to be checked by narrowing scope, recent change, and the current live signal before rollback. 실무에서는...ReviewedCI/CDBeginner3 minFreedocker build invalid reference format: the image tag is empty in GitHub Actionsdocker build invalid reference format: the image tag is empty in GitHub... is a hands-on troubleshooting drill. Learn how values pass between GitHub Actions steps. GitHub GitHub Actions Workflows needs to be checked by narrowing scope, recent change, and the current live signa...ReviewedCI/CDBeginner3 minFreeCICD-009Deployment failingA scenario that narrows down the root cause, centered on checking the permission-policy difference by event type, in the situation of a deployment failing because the secret is empty only on tag releases.ReviewedCI/CDIntermediate21 minFreeCICD-001Finding the real failure point in GitHub Actions build logsA training scenario for isolating the true cause from logs where npm dependency conflicts and cache traces are mixed together.ReviewedCI/CDIntermediate20 minFreeCICD-007Builds failingA scenario that narrows down the root cause, centered on realigning the cache key strategy and lockfile consistency, in the situation of builds failing because the cache key gets tangled after a Node version upgrade.ReviewedCI/CDBeginner16 minFreeCICD-109Self-hosted runner label matches the build queue but the runner misses the Docker socket mount and image builds fail only thereThe job lands on the intended runner group, yet one fleet member lacks the host capability the workflow assumes every labeled runner provides.ReviewedCI/CDIntermediate16 minFreeCICD-021Build cache key mismatch after lockfile updateA pipeline stays green on one branch and fails on another because the dependency cache key no longer matches the lockfile layout.ReviewedCI/CDBeginner17 minFreeCICD-038Publish workflow never startsA formatting or version-bump workflow commits successfully, but the downstream publish workflow never runs because the triggering push used the repository token.ReviewedCI/CDBeginner16 minFreeCICD-1611A GitHub Actions deploy is skippedOne deployment gate still points to the branch name used before renaming main.ReviewedCI/CDBeginner6 minFreeCICD-1615A Helm release uses old valuesOne CI release uses old values after a file rename.ReviewedCI/CDBeginner7 minFreeAn AWS access key was pushed to a public GitHub repositoryAn AWS access key was pushed to a public GitHub repository is a hands-on troubleshooting drill. Respond to a leaked cloud credential in the right order: revoke first, investigate, then clean up history. AWS Incident Response Operations needs to be checked by narrowing scope, r...ReviewedSecurityIntermediate18 minFreedocker push: denied: requested access to the resource is denieddocker push: denied: requested access to the resource is denied is a hands-on troubleshooting drill. Check which registry an image tag actually points to before debugging credentials. GitHub Container Image Delivery needs to be checked by narrowing scope, recent change, and th...ReviewedCI/CDBeginner14 minFreeCICD-098Maven cache reuse hides a repository auth failure until the monthly cache eviction windowBuilds appear stable for weeks, then all fail at once because the dependency cache had been masking a broken repository credential path.CI/CDIntermediate15 minFreeCICD-095Release branch hotfix bypasses the migration stepThe deployment is green, but the hotfix runs against an old schema because the branch-specific trigger skipped the migration workflow.CI/CDIntermediate17 minFreeCICD-030Release note generation fails on shallow clone runnersRelease note generation fails on shallow clone runners is a hands-on troubleshooting drill. A changelog step depends on full git history, but shallow checkout settings hide the required tags and commits. GitHub GitHub Actions Workflows needs to be checked by narrowing scope, r...CI/CDIntermediate18 minFreeCICD-092GitHub Actions reusable workflow loses required secretsThe shared pipeline is healthy overall, but one repository fails because the caller stopped forwarding the secret set the workflow expects.CI/CDIntermediate16 minFreeCICD-086Monorepo path filter skips the shared library change and one service deploys without rebuildingThe workflow optimization seems valid, but one service ships stale code because its dependency lives outside the path pattern that triggers rebuilds.CI/CDIntermediate16 minFreeCICD-108Artifact retention removes the SBOM before the security gate runs and attestation verification reports a missing dependency inventoryBuilds finish successfully, but the delayed security job cannot verify compliance because the artifact policy pruned the required software bill of materials too early.CI/CDIntermediate17 minFreeCICD-077GitHub Actions artifact download fails on self-hosted runnersThe workflow is correct, but only one runner cannot fetch artifacts because its local time drift makes a short-lived signed URL look expired immediately.CI/CDIntermediate17 minFree