Stuck backport PRs due to CLA confusion

[cjw296 (Chris Withers)]

Hello,

Not been here in a while, hope I’ve got the right part…
I merged this PR a couple of days ago, CLA is happy on this PR, but sad on the backports:

• [3.13] gh-150175: Fix ThreadingMock call_count race condition (GH-150176) by miss-islington · Pull Request #150180 · python/cpython · GitHub
• [3.14] gh-150175: Fix ThreadingMock call_count race condition (GH-150176) by miss-islington · Pull Request #150181 · python/cpython · GitHub
• [3.15] gh-150175: Fix ThreadingMock call_count race condition (GH-150176) by miss-islington · Pull Request #150182 · python/cpython · GitHub

How do I get this un-wedged so I can merge the backports?

[Stanfromireland (Stan Ulbrych)]

Hi Chris,

This is because the user has a different email configured for merges on GitHub than the one they used for commits in the PR. See the devguide for more information on the topic.

Best way to go forward is to ping the user and ask them to sign it (I went ahead and did this for you). If the backport is important and they don’t respond, then I suggest force-pushing commits with the previous email they used (and signed the CLA for) to the backports.