incident

Incident response for production issues requires a structured workflow to triage severity, investigate recent deployments, apply mitigation like rollbacks, and document a post-mortem. This ensures rapid resolution and future root cause analysis.

Triage a production incident by quickly assessing its severity and understanding the impact on critical services. This structured approach helps the on-call engineer gather necessary information to decide on an immediate course of action.

Yes, you can use GitHub CLI commands during incident investigation to check git history, review recent workflow runs, and analyze logs. This helps identify recent deployment changes that might have triggered the issue.

Mitigation options for a downed critical service include deploying rollbacks, toggling feature flags, or applying hotfixes. These actions stabilize the production environment while a permanent root cause resolution is developed.

Create a post-mortem after incident mitigation by using structured documentation to facilitate clear communication and creating follow-up issues. This documents the event for future learning and tracks root cause analysis.