github to email

[David Shea]

Github pull request stuff is now forwarded to anaconda-patches, using
this thing: https://github.com/dashea/github-email-hook

I can move it to rhinstaller if we feel like. The code is running on
OpenShift, somewhere in the Red Hat public cloud. The web hook and
associated cron job will email the list with:

- Patches in new and resynchronized (push --force, or just regular push
with new commits) pull requests
- comments on pull requests
- comments on the diff for a pull request ("Files changed" tab on the web)
- comments on the commits in the pull request made in the repo being
merged into (the ones listed for the pull request via the API, and hence
the ones linked to in the patch emails)
- comments on the commits in the pull request made in the repo being
merged from (the ones listed on the web, and the ones that need that
cron job)
- line-based comments on commits (both kinds), though there's no context
provided because that turned out to be harder than I wanted to deal with

If you find another way to comment on stuff, please let me know, and
also I hate you.

[Martin Kolman]

Post by David Shea
Github pull request stuff is now forwarded to anaconda-patches, using
this thing: https://github.com/dashea/github-email-hook
I can move it to rhinstaller if we feel like. The code is running on
OpenShift, somewhere in the Red Hat public cloud. The web hook and
- Patches in new and resynchronized (push --force, or just regular push
with new commits) pull requests
- comments on pull requests
- comments on the diff for a pull request ("Files changed" tab on the web)
- comments on the commits in the pull request made in the repo being
merged into (the ones listed for the pull request via the API, and hence
the ones linked to in the patch emails)
- comments on the commits in the pull request made in the repo being
merged from (the ones listed on the web, and the ones that need that
cron job)
- line-based comments on commits (both kinds), though there's no context
provided because that turned out to be harder than I wanted to deal with

Thanks! Looks nice so far! :)

Post by David Shea
If you find another way to comment on stuff, please let me know, and
also I hate you.
_______________________________________________
Anaconda-devel-list mailing list
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Vratislav Podzimek]

Post by David Shea
Github pull request stuff is now forwarded to anaconda-patches, using
this thing: https://github.com/dashea/github-email-hook
I can move it to rhinstaller if we feel like. The code is running on
OpenShift, somewhere in the Red Hat public cloud.

Nice use of OpenShift! Looks and works good so far, thanks!

[David Shea]

Post by Vratislav Podzimek

Post by David Shea
Github pull request stuff is now forwarded to anaconda-patches, using
this thing: https://github.com/dashea/github-email-hook
I can move it to rhinstaller if we feel like. The code is running on
OpenShift, somewhere in the Red Hat public cloud.

Nice use of OpenShift! Looks and works good so far, thanks!

Well, that didn't take long to break. The pull request that Colin
requested returned a 302 Found instead of actually doing anything, and
I'm not real sure why. I saw this once during testing, but I had hoped
it was just a fluke. Guess I should figure out what happened now.