The scheduled GitHub action gets disabled every 60 days #53
Description
After 60 days of inactivity, scheduled GitHub Actions get disabled by default.
In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days.
Source
As far as I can tell, there's no way around this limitation apart from
- "some outside system" (e.g. GitLabCI or AWS Lambda) poking in and re-enabling all auto-disabled schedules via the API or
- by having yet-another-schedule push dummy commits to the repository to keep it active/alive. (Someone has even created an action for this 🙄 keepalive-workflow)
Since we've run into this problem several times already, it'd be nice if we could solve it somehow. To the worst, we could notify ourselves on Slack if the period of inactivity is approaching.