Gah, I was hoping that was fixed (it seemed that it had been at a glance).

So the general issue is that it looks like the GitHub API isn't always picking up on activities in commits to trigger events.

That's disappointing

Bad stuff :(
I "think" we should run a cron and check periodically for updates - as an addition to the GitHub hooks - just in case ;)
Would that be an option ?

I'd support that. Would also be good for those eventual GitHub downtimes.

On Sunday, November 10, 2013, Nikolai Plath wrote:

Bad stuff :(
I "think" we should run a cron and check periodically for updates - as an
addition to the GitHub hooks - just in case ;)
Would that be an option ?

—
Reply to this email directly or view it on GitHub#175 (comment)
.

I thought about cron also. How often should it run - every hour or less may be?

Would this be a true, server-side cron, or traffic based pseudo-cron? If traffic based, could it be once every hour unless we exceed a certain traffic level?

So we already have a script to do these updates, add a true server-side cron job triggering that, have a nice day :-)

OK, so note, that script is only doing labels. But the update command can be expanded on or use the get command.

So we already have a script to do these updates, add a true server-side cron job triggering that, have a nice day :-)

Cool

What is the current status?

@mbabker can we close it?

Ya, we can. Cron jobs I think are working well enough for us now.