CI goes inactive due to long delays between releases

[alexpeterson91]

I've noticed several updates in the last year were missed or done right in the nick of time because a user or myself found it our nodes offline due to hard forks etc. I just realized yesterday the reason why we werent getting notified was because the CI actions go inactive after a certain amount of time and need to be manually restarted, i did that last night and 4 hours later the CI opened a PR and deployed the test package, @tropicar merged the commit. Im curious is there a way to extend the time before the actions go inactive? we have several smaller not widely used packages like this that have similar issues.

[tropicar]

I am unsure if that is the issue because although there are no releases, the github action should check the repository in order every x time defined in the cron. Anyway, I am researching that, and checking if there is some typo.

[alexpeterson91]

I'm almost sure it's the issue because when i got to the packsge it said GitHub actions were paused due to repo inactivity it's not the workflow code it seems to be a GitHub actions setting. I had to restart them clicking a button resume or restart GitHub actions. And then it worked. It may not be possible to change it it's probably set like this to save money on runners when a repo is inactive for a couple months.