Remove scheduled job in code.yaml
Closed this issue · 6 comments
As it gets disable if the project is not pushed to, and stops it running on PR
We discussed this a while back and decided:
- comment out the weekly build with a comment to say re-enable if needed
- maybe now we know that this can make GHA disable the workflow we should not recommend it?
- move the link check to a monthly cycle
- what should we do with this one? we can only let it run after first successful docs - but its a bit useless if it ends up getting diabled.
I think the weekly run of code.yaml is probably just noise, so we will delete it. The linkcheck.yaml however shouldn't break as often, and is useful to keep working as you can't "pin" your docs external references.
https://stackoverflow.com/questions/67184368/prevent-scheduled-github-actions-from-becoming-disabled
This suggests 60 days of no activity will set it inactive, but you can poke a REST API to re-enable it.
I suggest we don't commit to ibek until January 11th and see if this page shows as disabled:
https://github.com/epics-containers/ibek/actions/workflows/linkcheck.yml
If it does, then try pushing to the repo and see if it becomes re-enabled a week later. If it does then we are done. If it does not, then we will have to think about poking this API from within the linkcheck workflow.
The ibek scheduled job is still working, could be worth having a chat about this.
The ibek scheduled job is still working, could be worth having a chat about this.
It's probably only working because of dependabot. I will make a new repo from the skeleton and get back on this in 60 days.
Here's the repo
https://github.com/evalott100/Silly-Repo-That-Should-Go-Inactive
Looks like this is still a problem:
I think we should go ahead and remove the schedule from code.yaml, and add the keepalive-workflow as the last step of linkcheck