Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub may disable scheduled workflows in this repo #144

Open
bgilbert opened this issue Sep 30, 2023 · 0 comments
Open

GitHub may disable scheduled workflows in this repo #144

bgilbert opened this issue Sep 30, 2023 · 0 comments
Labels

Comments

@bgilbert
Copy link
Member

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.

bgilbert added a commit to bgilbert/openslide-bin that referenced this issue Sep 30, 2023
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant