as you all know, I was working on integrating GitHub into b.p.o under GSoC.
This email is a summary of my work.
Github PRs will be presented in a similar manner as mercurial repos, the
preview is available here
There will be three ways of linking GitHub PR to an issue on b.p.o
*1. Manually submit a link to GitHub PR on b.p.o*: Paste the link to the
new pull request in the newly-added field "GitHub PR" on issue page. Here
<https://github.com/AnishShah/GSoC/raw/master/manual.png> is how the new
field looks like.
*2. Automatically link GitHub PR using keywords*: If keywords like "fixes"
followed by issue number are used in PR title/body, then it is
automatically linked to that issue on b.p.o. For example, "fixes bpo123"
will link PR to issue 123 on http://bugs.python.org
*3. Auto conversion of a patch file to GitHub PR*: Submit a patch file like
same old way and it will be converted to a GitHub PR automatically.
The detailed description of all the patches I've submitted during my GSoC
can be viewed here
Thank you, everyone. It was great to work on this project.
Just FYI, there are some really cool new features in GitLab 8.11 announced
today. I haven't played with them yet, but the ones I'm excited about are:
* Kanban-like issue boards. Automatically generated from issue labels.
* Thru-the-web merge conflict resolution.
* Resolve discussions
* Online IDE integration.
I'm working on GitHub integration as a part of GSoC. One of my tasks was to
show GitHub review comments on b.p.o.
Here is how I did it :-
I wrote a handler to handle GitHub PR review/diff comments event using
webhooks. If a b.p.o issue is linked to a PR, then it checks if any
"GitHub" comment was added in last "X" minutes. If no GitHub comments were
added, then it adds that comment to the linked issue. This way there will
be fewer emails and also developers who are in the nosy list but are not
subscribed to GitHub PR will get notified about the progress/review
comments on PR. You can check the patch here
I wanted to know from you all if this is the right approach. If not, then
what should be changed?
I have recently set up several CI services in my cpython fork on
I am not ready to make any recommendations, but feel free to click on
the build badges at the top of the README file and see the results for
yourself. I activated the following services:
* Travis CI
* AppVeyor (windows)