Fixes as pull requests, not tickets

Arjun Nair working at a laptop and a portable dark monitor showing a graph with one magenta path

A ticket asks someone to work out the fix, find the right repository and make time for it. A pull request only asks for a review.

That difference decides whether a finding is closed this week or carried into next quarter. Engineers already know how to review a small change, and they trust it more than a report.

What goes in each one

  • One root cause, in the title, in plain words.
  • The smallest Terraform change that breaks it.
  • What used this permission in the last ninety days.
  • How to roll it back.

Nobody has ever been thanked for a ticket. Merging a clean fix takes two minutes.

Keep them small

One root cause per pull request. If a change touches thirty unrelated roles, nobody reviews it properly. On a sample payments platform, 37 small requests closed every Critical in 11 days, and none of them was rolled back.

About the author

Arjun leads customer engineering at Wardline and sits in the shared channel with every new team. Fictional author, demo content.

Related cloud notes