Stream: coq-community devs & users

Topic: GitHub disabling Actions


view this post on Zulip Karl Palmskog (Nov 13 2021 at 20:31):

OK, this is a new one for me: after 60 days without a commit which triggers an "Action" workflow, GitHub completely disables all actions for repo! One can reenable it manually, but really annoying...

view this post on Zulip Karl Palmskog (Nov 13 2021 at 20:32):

so basically, to have your cron jobs going, you have to keep doing useless commits

view this post on Zulip Théo Zimmermann (Nov 14 2021 at 19:14):

Yes, I've been puzzled by this behavior before (see https://github.com/coq/bignums/pull/54#issuecomment-876627240). Fortunately, it doesn't affect repositories that do not use schedule workflows AFAIU.

view this post on Zulip Théo Zimmermann (Nov 14 2021 at 19:15):

I can understand that GitHub doesn't want its server wasting time on cron jobs in dead projects. However, what I don't get is why GitHub Actions are not re-enabled automatically if there's another trigger (like a new commit or PR).

view this post on Zulip Emilio Jesús Gallego Arias (Nov 14 2021 at 19:17):

They likely have a reason, these days the abuse of CI services by crypto miners is a big issue unfortuantely

view this post on Zulip Théo Zimmermann (Nov 14 2021 at 19:20):

I'm guessing there's a reason indeed (e.g. not wasting time on inactive projects) and they implemented their solution in a quick way that is probably not the smartest.

view this post on Zulip Karl Palmskog (Nov 15 2021 at 08:53):

so essentially low-activity projects should never use cron jobs then

view this post on Zulip Théo Zimmermann (Nov 15 2021 at 11:27):

Or be prepared to manually turn Actions on every time they get disabled.


Last updated: Feb 05 2023 at 13:02 UTC