This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xtreak
Recipients brett.cannon, eamanu, xtreak
Date 2019-03-29.13:02:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1553864552.1.0.0868407062337.issue36472@roundup.psfhosted.org>
In-reply-to
Content
There were cases in the past where CLA was signed but there was mismatch in the bpo details and GitHub usernames linked due to which bot didn't change it to CLA signed. I would request this to be discussed in other channels like https://discuss.python.org/c/core-workflow or zulip core-workflow chat or mailing list. This issue could be closed since there is nothing that could be done in the bug tracker here. These problems might be solved by using CLA assistant. Closing a PR needs relevant access and I guess Brett is also reviewing PRs where CLA is not signed.
History
Date User Action Args
2019-03-29 13:02:32xtreaksetrecipients: + xtreak, brett.cannon, eamanu
2019-03-29 13:02:32xtreaksetmessageid: <1553864552.1.0.0868407062337.issue36472@roundup.psfhosted.org>
2019-03-29 13:02:32xtreaklinkissue36472 messages
2019-03-29 13:02:31xtreakcreate