First step towards GitHub integration

[Kubilay Kocak]

On 17/11/2014 4:57 PM, Craig Rodrigues wrote:
> git-admin,
> 
> Bartlomiej is interested in integrating github and Bugzilla via the github
> REST interface.
> Can you work with him to give him any access he needs to accomplish this?
> 
> I am not 100% sure on what Bartlomiej needs, but he may need
> to be able to set up commit hooks that use the REST API.
> 
> Can you help him?

Absolutely happy to assist.

I don't believe Github provides for a commit hook permission, so we may
have to set it up given instructions from robak at .

Bartłomiej, I'm available on IRC or if you'd like you can create a PR
with the relevant details and assign it to me.

> 
> Thanks.
> --
> Craig
> 
> On Sun, Nov 16, 2014 at 10:08 AM, Bartłomiej Rutkowski <robak at freebsd.org>
> wrote:
> 
>> Hi everyone,
>>
>> Following the recent discussion on the developers mailing list about
>> opening to wider audience by increasing our presence on GitHub (and
>> perhaps, in future, switching to Git) I volunteered to take care of the
>> very first step, that is - stop closing pull requests on GitHub without any
>> action on them.
>>
>> My first, rough, idea is to create a GitHub hook that would act on pull
>> requests aganist our repositories. Such hook would call an application,
>> written by me (some sort of REST-ish Python based application, small thing)
>> hosted on our infrastructure, that would get the pull request data in JSON
>> from that hook call, validate it, and after proper transformation (not sure
>> yet how much, if any, will be required) send it to our Bugzilla via XMLRPC
>> interface.
>>
>> Once such PR is successfuly created, it would then send back a link to
>> that PR and some additional information (encouraging the original sender to
>> create his Bugzilla account, reach out to us on mailing lists, IRC and so
>> on) as a comment to the original pull request, closing it at the same time.
>>
>> So, that's the idea for the very first step, very limited, one way only,
>> no bells&whistles, but the idea behind is to do one thing and one thing
>> only, yet to do it well. Comments welcome! :)
>>
>