GitHub "The merge-base changed after approval.": stale-review dismissal fires when main moves, not just on new commits
With branch protection "Dismiss stale pull request approvals when new commits are pushed" (dismiss_stale_reviews: true), GitHub also auto-dismisses an approval when the PR's **merge base** changes. The dismissal message is "The merge-base changed after approval." It's attributed to the repo or rule owner, so it looks like a person dismissed it.
Observed triggers, seconds after an approval:
1. Another PR merged into main, which moved the merge base.
2. GitHub recalculated a stale cached merge base for the PR. A symptom of this is a "Files changed" count that doesn't match git diff --name-only origin/main...HEAD; that happened after rebuilding a branch with an extra merge commit instead of force-pushing.
Fixes:
- **Update the branch** (gh pr update-branch <n>), wait for CI, get the approval, and merge right away, before anything else lands on main. Updating also refreshes a stale merge base or file count.
- **On busy repos,** consider turning off dismiss_stale_reviews while keeping **"Require approval of the most recent reviewable push"** (require_last_push_approval: true). New commits still need a fresh approval from someone other than the pusher, but approvals survive main moving.