Git hub : CLA Not Signed label
All, I submitted two Pull Requests last Sunday, only a few hours after I signed the CLA. I understand why the 'Knights who say ni' marked the Pull request as 'CLA Not Signed' Label at the time I submitted the Pull requests, but I was wondering when the Labels get reset. How often (if at all) does the bot look at old pull requests ? Thanks for any help you can give, I am sorry if the question sounds basic.
On Mar 10, 2018, at 21:58, Anthony Flury via Python-Dev <python-dev@python.org> wrote:
I submitted two Pull Requests last Sunday, only a few hours after I signed the CLA.
I understand why the 'Knights who say ni' marked the Pull request as 'CLA Not Signed' Label at the time I submitted the Pull requests, but I was wondering when the Labels get reset.
I've reset both manually. Thanks for the heads up. Now to get reviews! -- Ned Deily nad@python.org -- []
On 3/10/2018 9:58 PM, Anthony Flury via Python-Dev wrote:
All, I submitted two Pull Requests last Sunday, only a few hours after I signed the CLA.
When processed properly, a day to a week, usually, a * will appear after your name on any tracker (bpo) post.
I understand why the 'Knights who say ni' marked the Pull request as 'CLA Not Signed' Label at the time I submitted the Pull requests, but I was wondering when the Labels get reset.
When a core developer manually removes the label, as Ned did, and the bot checks with the tracker and agrees.
How often (if at all) does the bot look at old pull requests ?
Never, that I know of.
Thanks for any help you can give, I am sorry if the question sounds basic.
One can also request help on core-mentorship list. A link to the PR helps. -- Terry Jan Reedy
On 2018-03-11, 03:45 GMT, Terry Reedy wrote:
When processed properly, a day to a week, usually, a * will appear after your name on any tracker (bpo) post.
So, I got my start after the name, where is the list of maintainers of individual packages, so I could know whom to bother to take a look at my PR https://github.com/python/cpython/pull/5999 (damn, just one number too small!). Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. -- C. A. R. Hoare
On 3/11/2018 3:34 AM, Matěj Cepl wrote:
On 2018-03-11, 03:45 GMT, Terry Reedy wrote:
When processed properly, a day to a week, usually, a * will appear after your name on any tracker (bpo) post.
So, I got my start after the name, where is the list of maintainers of individual packages, so I could know whom to bother to take a look at my PR https://github.com/python/cpython/pull/5999 (damn, just one number too small!).
https://devguide.python.org/experts/ I added Langa for configparser. I have no idea what is going on with the numerous errors, like ====================================================================== ERROR: test_write_filename (test.test_configparser.SortedTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "C:\projects\cpython\lib\test\test_configparser.py", line 717, in test_write_filename os.unlink(f.name) PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'C:\\Users\\appveyor\\AppData\\Local\\Temp\\1\\tmpklkbe8_y' -- Terry Jan Reedy
participants (4)
-
Anthony Flury -
Matěj Cepl -
Ned Deily -
Terry Reedy