Sometimes we need to deviate from the usual process. The typical case is when a build breaks at some silly place, not related to the change. Surely, we can go and try to figure out why the build was broken – which sometimes is related to the infrastructure, sometimes it is a race condition in someone else's test, sometimes it's bad build configuration. Fixing that all takes time, and it should be fixed, except in the cases where merge is required now. What currently happens in those cases is: I would go and disable PR merge requirements, do the merge, and then enable them back.

What I'd rather have:

1. Allow the admin to set up a group of users who can override PR merge constraints
2. Add another menu item in the "..." dropdown called "Force Merge" or something like that
3. When this action is invoked, a dialog appears, which requires the user to enter a non-empty explanation about why the merge is forced.
4. Historically, forced merges are marked and the explanation is shown in the PR details.

While achieving the same result, it is much better because there's clear traceability to the override actions.