GitHub
682 incident problems in GitHub environments.
먼저 읽을 가이드
추천 문제
All problems (682)
CICD-1267A reusable workflow deploys correctly in the caller but silently loses its secret in the called workflowA team modularizes its deployment pipeline and later finds that the reusable workflow cannot access credentials that were available in the original monolithic version.CI/CDIntermediate16 minProCICD-1274A reusable workflow inherits the caller repository but not its permissions, so the deployment step fails after modularization even though the old monolithic job workedThe refactor succeeds syntactically, yet the new called workflow loses privileges because the permissions contract changed at the workflow-call boundary.CI/CDIntermediate16 minProCICD-1278A workflow can clone the main repo but submodule fetch still failsA monorepo with private submodules starts failing only after nested repositories are switched to SSH references.CI/CDIntermediate16 minProCICD-1257A workflow can run shell steps on a self-hosted runner but Docker actions failA team migrates to a self-hosted build host and discovers only Docker-backed actions fail while ordinary shell steps succeed.CI/CDIntermediate16 minProCICD-1252A workflow correctly generates the release notes but the approval gate still blocksA release gate depends on generated metadata and later blocks only after a change that moved the same content into a human-readable summary.CI/CDIntermediate16 minProCICD-1247A workflow summary renders the right markdown but the gate step still failsA team trusts the visible summary page and misses that the blocking gate is still reading an empty or truncated machine output channel.CI/CDIntermediate16 minProCICD-1229Deployment waits forever on required checksA workflow refactor adds matrix expansion and pull requests begin hanging on a required check that is technically present only under old naming.CI/CDIntermediate16 minProCICD-1239A branch deploy runs from the correct ref but publishes the wrong static bundleA matrix build produces multiple platform or environment bundles and one deployment job later downloads the wrong one under a reused artifact name.CI/CDIntermediate17 minProCICD-1254A matrix build reports green but the deploy downloads the wrong packageA multi-platform or multi-region build fan-out completes and later one deployment installs the bundle from another variant.CI/CDIntermediate17 minProCICD-306A preview deployment signs in with a lower-privilege identity and the later promote step assumes those same credentials are still sufficient during a failover rehearsalThe early environment works, but the promotion path needs a broader scope that the pipeline never refreshes. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDIntermediate17 minProCICD-345A release workflow restores a cached dependency graph that no longer matches the promoted lockfile lineage during a staged decommissionBuild reproducibility appears intact, but the promoted dependency graph was reconstructed from stale lineage metadata. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.CI/CDAdvanced17 minProCICD-1234A reusable test workflow publishes clean results but the caller still marks the run failedA diagnostic or flaky-report step should be informational, but the calling workflow still blocks merge because the status contract was not separated cleanly.CI/CDIntermediate17 minProCICD-1249An artifact upload succeeds but a later job downloads an empty bundleA build step writes files after creating the archive path, and a downstream consumer later downloads an artifact that looks valid but has no useful payload.CI/CDIntermediate17 minProCICD-1215Deployment waits foreverA centralized reusable deploy flow still shows a waiting gate after an environment approval was already granted.CI/CDIntermediate17 minProCICD-1219Environment file generation succeeds but later steps read stale valuesA deploy job keeps using an old endpoint even though the pipeline visibly generated the new env file earlier.CI/CDIntermediate17 minProCICD-1227Package restore succeeds but the later build still uses the old dependency graphA monorepo branch changes one workspace lockfile and CI still behaves as if the old dependency tree is present.CI/CDIntermediate17 minProCICD-121Protected environment reviewers are configured, but a branch rename leaves the production rule attached to the old pattern and deployment bypasses approvalThe release pipeline still sees a valid environment, yet the protection logic no longer matches the new main branch name the team now uses.CI/CDAdvanced17 minProCICD-1224Scheduled workflow behaves differently from manual dispatchA nightly deployment behaves differently than the manually triggered path even though both invoke the same workflow file.CI/CDIntermediate17 minProCICD-282A deployment gate reuses the latest successful build from the wrong branch lineage during a failover rehearsalThe artifact is valid, but the gate promotes a build that never belonged to the current release branch. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDAdvanced18 minProCICD-264A self-hosted runner image refresh changes the Docker builder version and breaks layer cache reproducibility across the fleet during a failover rehearsalBuilds still run, but cache keys and layer outputs diverge between old and new executors. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.CI/CDAdvanced18 minPro