[1f60c]

AFAIK, scheduled GitHub workflows stop running after a while. But when that happens, GitHub will send you an email with a big green “Continue running workflow” button.

[prepend]

Actions won’t run on repos with no activity for 60 days [0]. So make sure your action commits something to the repo to keep up activity.

This seems to meet OP’s use case as they have to commit state anyway.

[0] https://docs.github.com/en/actions/managing-workflow-runs/di...

[akerl_]

I use crons to keep my Docker containers fresh, and have never hit this. But the cron commits to the repo, so I wonder if they’re flagging repos with crons but no commits recently?

[tracker1]

Definitely... It seems to be in 4-6 week timeframe... I'd thought about making the cron update references in the repo, but hadn't gone through that as of yet.

[tracker1]

I've got a couple projects like this, that mostly just create bundles of other source projects that I'm not involved with. Creating a windows installer, or docker image for projects that don't have that integrated. It's kind of annoying that they will stop in several weeks when there's no project changes.

[moehm]

> It's kind of annoying that they will stop in several weeks when there's no project changes.

Can't you configure a GHA which commits nonsense every month?

[tracker1]

Yeah... I will probably do that, with my daily check action (update a last-check) text file or something.

[genericacct]

Can you not trigger an action via a local cronjob and the API?

[tracker1]

But then I need a second system to do that.

[sauruk]

sounds like time to make a “hit the big green button” github action

[WirelessGigabit]

I wonder if I can make a Github repo with an action that commits to another repo on a cron. Or itself?