Hi, I like this idea. Checker is not for us. It is for all autotest developers which tries to send patch to github. In my opinion it is good way how to inform developers about common problems in theirs code without long waiting. It could be more confortable for them.
Have a nice day, Jiří Župka ----- Original Message ----- > Dne 12.2.2014 20:29, Chris Evich napsal(a): > > On 02/12/2014 10:48 AM, Lukáš Doktor wrote: > >> Hi Chris, this is only very basic checker to have some data before we > >> can talk about the need of something like this. So no caching, no > >> optimization and no API-rate control is required. > > > > Yep, gotcha, was just a FYI in case it gets bigger. I've got some code > > floating around to do the caching, if needed I can dig it up and dust it > > off. > > > > Yeah, thank you for the offer, I'll keep that in mind. > > Currently the traffic is not too bad: > 1 + no_pull_request to discover nothing changed > no_changed_pull_request to update changed pull request (easily reducible > by storing get_commits() output) > no_changed_pull_request to update messages > > let's say we run this script every quarter of hour on all repos... > That's not so bad. Plus most of the time I need fresh data... > > Anyway these are just details, any ideas about the necessity of the tool? > > _______________________________________________ > Virt-test-devel mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/virt-test-devel > _______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
