"Why do I need to sign the CLA again?"

[hugovk]

It's often confusing when the CLA bot asks you to sign the CLA for a backport, when you've already signed it for the original PR.

Let's add a section we can share on PRs.

---

📚 Documentation preview 📚: https://cpython-devguide--1680.org.readthedocs.build/getting-started/pull-request-lifecycle/#why-do-i-need-to-sign-the-cla-again

[efimov-mikhail]

LGTM.

Maybe we want to add small piece of information about signing CLA again not only in case of backports but also in case when git email was changed? It's also possible, I've remember examples of this even for core devs.

[hugovk]

Maybe we want to add small piece of information about signing CLA again not only in case of backports but also in case when git email was changed? It's also possible, I've remember examples of this even for core devs.

Yeah, I considered that, but thought it's better to just cover the very common case, than make it more general/less specific/longer.

For those cases, we can point to the same thing and say "sign with your new email, it's kind of like this".

And we can always improve this later.

Thanks for the reviews!