An emergency scenario is a code-review situation where urgent circumstances make the regular approval process impractical. It permits a controlled exception without treating the exception as the new default. section 3.4.1
A defensible emergency exception combines several safeguards:
- Mark the pull request with an emergency tag. section 3.4.1
- Permit author self-approval only for tagged emergencies, while preserving the regular process for ordinary changes. section 3.4.1
- Require a justification after self-approval; linking the related bug report can satisfy the emergency rationale. section 3.4.1
- Consider expanding emergency approver access to next-level managers instead of allowing self-approval. section 3.4.1
Emergency pull request
A developer submits an urgent fix, adds the emergency tag, and self-approves it because no regular approver is available. The linked bug report records why the exception was necessary. section 3.4.1
