I just saw this https://github.com/pyupio/octohook and thought it might be useful for CPython’s Github hooks.
-----------------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
https://www.python.org/dev/peps/pep-0512/#define-commands-to-move-a-mercuri…
There appear to be multiple ways to convert hg repos to git, but no clear
winner. It would be great if some one/people took on the task of evaluating
the tools available out there by converting the cpython repo and seeing
which one has the best results.
https://www.python.org/dev/peps/pep-0512/#adding-github-username-support-to…
In order for the CLA bot to work, I need people to be able to add their
GitHub usernames to their bugs.python.org profile. I also need some API(s)
that I can hit from the bot that lets me pass in a GitHub username -- or
names, since there can be more than one, but I'm also fine making multiple
individual requests instead of multiple names in a single request -- and
get back some kind of signed/not signed/no GitHub username response (can
even be GitHub username -> b.p.o username in one call and then b.p.o CLA
status as another if that's easier).
I'm not sure if Ezio was planning to own this or not, so I'm asking if
anyone wants to take this on or help Ezio with the work if he does want to
lead it (or R. David if he wants to lead it).
I was at linux.conf.au 2016 last week, and one of the presentations
was from Mozilla's Emily Dunham on some of the infrastructure
automation they use with Rust and other GitHub based projects:
https://www.youtube.com/watch?v=dIageYT0Vgg
In addition to their merge bot project homu (which we've talked about
previously), they also have:
highfive (a greeter bot): https://github.com/nrc/highfive
starters (an issue curator): https://starters.servo.org/
The first project looks for folks submitting their first PR or issue,
and responds with some standard info to save humans from having to do
it later (like pointers to the Code of Conduct and the Contributor
Licensing Agreement, as well as explanations of how the contribution
process works)
The second one is designed to provide a better answer to the "How do I
get started?" question by making it easy for developers to tag simpler
issues. This could presumably also be used to provide separate views
based on what folks want to work on (e.g. documentation, Python code,
C code)
While these wouldn't necessarily be something we wanted to set up
immediately, it likely makes a lot of sense to try to share the tool
maintenance load with Mozilla rather than going for a completely
custom setup.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia