Let admins merge past branch protections from the PR merge dialog (like gh pr merge --admin)

[pzep1]

On some repos I work in, branch protection needs a code owner's review that I can't give on my own PRs. I'm an admin on those repos, so GitHub lets me merge past that, and gh pr merge --admin works fine from a terminal.

In T3 Code there's no way to do the same. Turning on auto-merge either fails with "Could not turn on auto-merge: The host refused it…" or sits there waiting for a review that's never coming. So I drop out to the terminal for something the app already almost does.

Proposal: when GitHub reports viewerCanMergeAsAdmin: true for the viewer, show a Merge now as an administrator checkbox in the existing merge and auto-merge confirm dialogs. Ticking it does exactly what gh pr merge --admin does: a direct mergePullRequest call that skips auto-merge and the merge queue.

• Only viewers GitHub already allows to bypass protections ever see it. Nobody gains a permission they don't already have.
• It's off by default, resets every time the dialog closes, and the dialog turns into a clearly destructive "Merge as administrator?" confirm when it's ticked.
• GitHub only. Other hosts never see it.

It's small: one extra GraphQL field, one optional flag on the existing merge action, and a checkbox. I've got an implementation with tests and screenshots in #17281 if the direction sounds OK.

[gustavohariel]

Same need on Gitea/Forgejo, so adding the use case here instead of a separate Idea.

On a protected branch that requires approvals, a repo admin merging from the PR panel gets HTTP 405 "Does not have enough approvals". The Gitea web UI shows "As an administrator, you may still merge this pull request" and lets the merge through. The host only allows it when the merge request sets force_merge: true; T3's Forgejo provider sends only Do. force_merge is part of the public merge API on both Gitea and Forgejo.

If the GitHub direction here is approved, the Forgejo/Gitea equivalent could follow the same shape: an explicit, off-by-default "merge as administrator" choice. It would appear only when the repo reports permissions.admin: true and the merge was refused by protection. That sends force_merge: true and nothing else changes. Gitea still rejects it when the rule has "block admin merge override" enabled, and the server's error would be shown as-is.