We have a standard... no one promotes their own code... period.

We also have another standard that identifies the development, testing, and production deployment processes including peer review, QA and UAT.  For emergencies, we do the exact same thing but faster.  Each person is on the spot to take action as soon as the code responsibility is passed to them.

Finally, code doesn't move until the stakeholder(s) and the Dev Manager sign off on the ticket.  For emergencies, all of that has taken as little as 10 minutes depending on the needed change.

The good part is, because of the process that we stick to, we might have only 1 or 2 emergencies a year... usually, it's none per year.