GitHub
682 incident problems in GitHub environments.
먼저 읽을 가이드
추천 문제
All problems (682)
CICD-1286A workflow succeeds in one branch but fails in anotherA generated certificate, JSON blob, or changelog is written to GITHUB_ENV and only some branches or shells later consume a broken value.CI/CDIntermediate14 minProCICD-381A pipeline pins the runner image while the fetched bootstrap script still resolves the latest policy bundle from a mutable channel during a staged decommissionThe execution environment is frozen and its policy input is not. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.CI/CDIntermediate15 minProCICD-140A release notes bot creates the Git tag before the artifact upload finalizes, and downstream consumers fetch a version with no binaries yetThe version appears published to automation, but its payload is still in flight when the deployment job tries to consume it.CI/CDIntermediate15 minProCICD-146A self-hosted runner group is moved to a new subnet, but the internal package mirror allowlist still trusts only the previous CIDRThe jobs land correctly, yet dependency downloads fail because network identity changed while the workflow labels stayed the same.CI/CDIntermediate15 minProCICD-156A test flake suppressor matches any timeout string, and the real deadlock regression gets auto-muted during release qualificationNoise reduction automation masks the exact new symptom the release gate was meant to catch.CI/CDIntermediate15 minProCICD-149The build step caches test reports by branch name, and a recreated hotfix branch reuses stale pass results from the previous incidentNo tests actually ran for the new code, but the cache key made the workflow appear green.CI/CDIntermediate15 minProCICD-198A branch-based cache key reuses stale test evidence during a failover rehearsalThe workflow turns green even though the current code path never executed fresh validation. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate16 minProCICD-131A change-approval webhook retries on timeout and opens duplicate maintenance windows for the same deploymentOne release becomes two approved windows because the idempotency key was not preserved across retries.CI/CDIntermediate16 minProCICD-152A shared action pins the Node runtime version, but the hosted runner image removes that runtime minor line and every workflow begins failing at startupNo application code changed, yet the execution substrate stopped honoring the action's implicit runtime dependency.CI/CDIntermediate16 minProCICD-318A shared workflow pins an action SHA while the action still downloads a floating helper tool version at runtime during a failover rehearsalThe action reference looks immutable, yet part of the execution path still depends on mutable remote state. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate16 minProCICD-154The monorepo release graph marks a shared schema package as optional, and one dependent service never rebuilds after a contract changeDependency topology is encoded in automation, but one edge was weakened until the next schema evolution exposed it.CI/CDIntermediate16 minProCICD-246A monorepo release train publishes service code before the shared contract package reaches the private registry mirror during a failover rehearsalApplication code moves ahead of the contract library and consumers resolve inconsistent dependency sets. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate17 minProCICD-497A pipeline pins the runner image (Rollout Stuck)A pipeline pins the runner image (Rollout Stuck) focuses on ci-cd-workflow-debugging and asks the reader to isolate Rollout Stuck in GitHub. 실무에서는 ci-cd-workflow-debugging 문제를 볼 때 실패 단계만 보지 말고 최근 변경, 이미지 태그, 시크릿 주입, 롤백 가능 여부를 먼저 함께 확인하는 편이 빠릅니다.CI/CDIntermediate17 minProCICD-499A pipeline pins the runner image (Rollout Stuck)A pipeline pins the runner image (Rollout Stuck) focuses on ci-cd-workflow-debugging and asks the reader to isolate Rollout Stuck in GitHub. 실무에서는 ci-cd-workflow-debugging 문제를 볼 때 실패 단계만 보지 말고 최근 변경, 이미지 태그, 시크릿 주입, 롤백 가능 여부를 먼저 함께 확인하는 편이 빠릅니다.CI/CDIntermediate17 minProCICD-501A pipeline pins the runner image (Rollout Stuck)A pipeline pins the runner image (Rollout Stuck) focuses on ci-cd-workflow-debugging and asks the reader to isolate Rollout Stuck in GitHub. 실무에서는 ci-cd-workflow-debugging 문제를 볼 때 실패 단계만 보지 말고 최근 변경, 이미지 태그, 시크릿 주입, 롤백 가능 여부를 먼저 함께 확인하는 편이 빠릅니다.CI/CDIntermediate17 minProCICD-560A pipeline pins the runner image (Rollout Stuck)A pipeline pins the runner image (Rollout Stuck) focuses on ci-cd-workflow-debugging and asks the reader to isolate Rollout Stuck in GitHub. 실무에서는 ci-cd-workflow-debugging 문제를 볼 때 실패 단계만 보지 말고 최근 변경, 이미지 태그, 시크릿 주입, 롤백 가능 여부를 먼저 함께 확인하는 편이 빠릅니다.CI/CDIntermediate19 minProCICD-035Self-hosted runner checkout fails after Docker step leaves root-owned workspaceA container-based build step finishes green, but the next checkout or cleanup fails because files written in the workspace are owned by root instead of the runner user.CI/CDIntermediate23 minProCICD-1620An Argo CD sync is green and one deployment still loads the wrong imageOne Argo CD workload still loads the wrong image after digest pin cleanup.CI/CDIntermediate10 minProCICD-1710A blue-green swap completes and one webhook consumer still failsA webhook consumer still fails after a blue-green swap looks complete.CI/CDIntermediate11 minProCICD-1760A canary deploy is green and one consumer still breaksOne consumer still breaks after a green canary deploy.CI/CDIntermediate11 minPro