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...
so basically, to have your cron jobs going, you have to keep doing useless commits
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.
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).
They likely have a reason, these days the abuse of CI services by crypto miners is a big issue unfortuantely
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.
so essentially low-activity projects should never use cron jobs then
Or be prepared to manually turn Actions on every time they get disabled.
Last updated: Jun 03 2023 at 15:31 UTC