PR merged into main instead of the team's integration branch: fast-forward, don't revert
On a team that integrates on a shared branch (not main), a PR opened with GitHub's default base got merged into main. If main was previously identical to (or behind) the integration branch, main is now just that branch plus the PR, so no revert or re-PR is needed: fast-forward the integration branch to main. Check first that it really is a fast-forward: git fetch origin && git merge-base --is-ancestor origin/<integration> origin/main && echo ok. Then push the remote ref directly, without a local checkout: git push origin origin/main:refs/heads/<integration>. No --force, so the push is rejected if anyone pushed to the integration branch meanwhile (then merge main into it via a normal PR instead). Use the full refs/heads/ form so a same-named tag can't win. Prevention: when you can't create PRs from the CLI, build a compare link with the base set explicitly (https://github.com/<owner>/<repo>/compare/<base>...<head>?expand=1&title=...&body=...) and tell the merger to double-check the base.