← Problem Library
CI/CD L6 CICD-011 · 17 min

Branch protection rules exist, but the deploy workflow pushes directly to main

Covers a deployment-policy problem where code-review protection exists but the automation account becomes a bypass path.

CI/CDIncident LeadershipLevel 6Team17 min
Scenario

A scenario that narrows down the root cause, centered on redesigning the permission boundary between human and automation accounts, in the situation of branch protection rules existing but the deploy workflow pushing directly to main.

What to check first
  • Identify the primary failure signal in the Release Policy scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.