Here’s my clucky work around.

“cherry pick”

git cherry-pick 723e16c
git cherry-pick --continue
  1. Create a new branch off the target branch.
  2. Cherry pick the commit that seems to be throwing the error incorrectly. Apply it to your new branch.
  3. Setup a new pull request from this new branch.
  4. Assuming that new pull request merges successfully, your original pull request should now also progress.

Yes it will create another commit which is sad but it will get things moving.

Does anyone know why this happens? Is it “squash merge” related?