Showing content from http://mail.python.org/pipermail/python-dev/attachments/20181019/be5a36c1/attachment.html below:
<div dir="ltr"><div>Of those 49 PRs, 18 are by core developers themselves, so 31 PRs are by external contributors that seem ready to be merged.</div><div><br></div><div>There was a discussion at one point on core-workflow about changing the default "needs" label for PRs by core devs which in this instance would help with providing a search for PRs that are possibly very close to being ready to be merged.<br></div><div><div><br><div class="gmail_quote"><div dir="ltr">On Fri, 19 Oct 2018 at 09:58, Stephane Wirtel <<a href="mailto:stephane@wirtel.be">stephane@wirtel.be</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
How are you? I am fine ;-) and you?<br>
<br>
So, on this morning I was playing with the github interface and the<br>
pull requests of CPython and I have discovered the advanced search of<br>
Github and I think this one is really useful for us and certainly for<br>
the core-dev.<br>
<br>
So, I was interested by somes PRs.<br>
<br>
PRs with this status:<br>
* open<br>
* review is approved<br>
* status of the CI is 'success'<br>
* has labels "awaiting merge", "CLA signed" and -"DO-NOT-MERGE"<br>
<br>
total: 49 PRs<br>
<br>
In the GitHub interface, here is the criteria<br>
<br>
is:open is:pr review:approved status:success label:"awaiting merge" -label:"DO-NOT-MERGE" label:""LA signed""<br>
<br>
But if you want to see the result in your browser, just click on this link.<br>
<a href="https://github.com/python/cpython/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+review%3Aapproved+status%3Asuccess+label%3A%22awaiting+merge%22+-label%3A%22DO-NOT-MERGE%22+label%3A%22CLA+signed%22" rel="noreferrer" target="_blank">https://github.com/python/cpython/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+review%3Aapproved+status%3Asuccess+label%3A%22awaiting+merge%22+-label%3A%22DO-NOT-MERGE%22+label%3A%22CLA+signed%22</a><br>
<br>
Here are the numbers:<br>
<br>
* just open: 959<br>
  is:open<br>
* and with label "CLA signed": 900<br>
  label:"CLA signed"<br>
* and with label "awaiting merge": 169<br>
  label:"awaiting merge"<br>
* and without label "DO-NOT-MERGE": 152<br>
  -label:"DO-NOT-MERGE"<br>
* with CI is happy ;-): 112<br>
  status:success<br>
* with review is approved: 49<br>
  review:approved<br>
<br>
total: 49 PRs could be merged.<br>
<br>
I was really surprised by this tool, (doc:<br>
<a href="https://help.github.com/articles/searching-issues-and-pull-requests/" rel="noreferrer" target="_blank">https://help.github.com/articles/searching-issues-and-pull-requests/</a>)<br>
<br>
But I was thinking about one thing, how can I help the core-devs to<br>
merge these PRs?<br>
<br>
Each week, I can send a report to this ML with the "mergeable" PRs.<br>
This kind of report could be useful for you?<br>
<br>
<br>
Have a nice day,<br>
<br>
Stéphane<br>
<br>
-- <br>
Stéphane Wirtel - <a href="https://wirtel.be" rel="noreferrer" target="_blank">https://wirtel.be</a> - @matrixise<br>
_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org" target="_blank">Python-Dev@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-dev" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="https://mail.python.org/mailman/options/python-dev/brett%40python.org" rel="noreferrer" target="_blank">https://mail.python.org/mailman/options/python-dev/brett%40python.org</a><br>
</blockquote></div></div></div></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4