Q: A developer pushed directly to the `main` branch and broke production. How do you prevent this?
Branch protection rules (GitHub/GitLab):
Want to master this scenario in a live sandbox? KodeKloud's Enterprise GitOps with ArgoCD & Kubernetes Rollouts covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "During a high-stakes release, we hit a similar deployment challenge and resolved it with automated safeguards. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
Branch protection rules (GitHub/GitLab):
- Require pull requests — no direct pushes to main. All changes must go through a PR.
- Require approvals — at least 1 (or 2) reviewers must approve before merge.
- Require status checks — CI must pass before merge is allowed.
Remediation & Permanent Safeguards
Even for small teams: enforce PRs. It takes 10 minutes to set up branch protection and can prevent hours of incident recovery.
- Require linear history — no merge commits allowed, must rebase. Keeps history clean.
- Restrict who can push — only CI service accounts can push to protected branches.
- Require pull requests — no direct pushes to main. All changes must go through a PR.
- Require approvals — at least 1 (or 2) reviewers must approve before merge.
- Require status checks — CI must pass before merge is allowed.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Promoting application releases to production without an automated, canary-validated rollback mechanism when configuring developer pushed directly Pipelines that lack automated rollback mechanisms force engineering teams to scramble manual hotfixes during severe production regressions.
- Running concurrent deployment pipeline jobs without stage mutex locking on shared target environments when configuring developer pushed directly Concurrent pipeline runs on the same environment race to apply state changes, causing out-of-order commits and unpredictable deployment state.
- Omitting dependency lockfiles (package-lock.json, go.sum, Cargo.lock) from continuous integration builds when configuring developer pushed directly Omitting lockfiles allows upstream package updates to break builds unpredictably without any changes to application codebase.
- Failing to define dynamic cache invalidation keys for CI package managers and layer caches when configuring developer pushed directly Stale build caches mask underlying dependency incompatibilities or pull outdated libraries, while un-cached runs slow feedback loops.