3 ms·
Also note that Github will deactivate cron actions if there is no activity in the repo for 60 days. https://github.community/t/do-disabled-scheduled-workflows-
by Fileformat 5y ago
Also note that Github will deactivate cron actions if there is no activity in the repo for 60 days.
https://github.community/t/do-disabled-scheduled-workflows-re-activate-on-repository-activity/160658 https://github.community/t/do-disabled-scheduled-workflows-r...
- OJFord 5y agoBut you do get an email warning you, with a button to say 'no, keep going'. (I maintain docker images for gocryptfs & mergerfs - https://github.com/OJFord/docker-gocryptfs https://github.com/OJFord/docker-gocryptfs https://github.com/OJFord/docker-mergerfs https://github.com/OJFord/docker-mergerfs - that check for updates to those respective projects and push an updated image; if there's no new upstream version for a while then I get that email and have to click it to keep it running.)
- koolba 5y agoObviously you can automate that with another repo that has a cron job to push a dummy commit every 30 days.
- danappelxx 5y agoIn fact, they can play ping pong and keep each other going forever :)
- adobrawy 5y agoYou don't need seperate repository for that. You can use Personal Access Token & self-push.
- motoboi 5y agoI have a crown action which commits its own log. So, always active!