You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub disables scheduled workflows if a repository is inactive for 60 days. This repo has scheduled workflows to check for software updates and to periodically rebuild the container, and we'd like those to stay enabled.
openslide/builds commits to itself at least once a month to keep the repo active, but we probably don't want to create spurious commits here. It's not clear whether other events count as activity. Ideally we could do something that doesn't generate notifications, such as automatically editing a comment on an existing issue, or automatically disabling and re-enabling scheduled workflows via gh.
On the other hand, if we have at least one dependency update every two months, and the update PRs do in fact land, the repository will stay active without any special tooling.
The text was updated successfully, but these errors were encountered:
The container rebuild workflow has always lived here, but the scheduled
rebuild has historically run from the openslide/builds repo. The sole
reason for this indirection is that openslide/builds has logic to keep the
repository active, so GitHub doesn't disable scheduled jobs after 60 days
of inactivity. Now that we have periodic update-checking in this repo, we
have that problem here anyway:
openslide#144
Move the timer out of openslide/builds to simplify.
Signed-off-by: Benjamin Gilbert <[email protected]>
GitHub disables scheduled workflows if a repository is inactive for 60 days. This repo has scheduled workflows to check for software updates and to periodically rebuild the container, and we'd like those to stay enabled.
openslide/builds
commits to itself at least once a month to keep the repo active, but we probably don't want to create spurious commits here. It's not clear whether other events count as activity. Ideally we could do something that doesn't generate notifications, such as automatically editing a comment on an existing issue, or automatically disabling and re-enabling scheduled workflows viagh
.On the other hand, if we have at least one dependency update every two months, and the update PRs do in fact land, the repository will stay active without any special tooling.
The text was updated successfully, but these errors were encountered: