Skip to content

Commit 36fe012

Browse files
committed
keepalive: run twice a month
The reason for the keepalive workflow is that scheduled workflows are disabled in repositories that are "not active". The `gitgitgadget-workflows` repository, however, _is_ active, even if there are no code changes. In fact, the hope is that there won't be any need for code changes at some stage because the code is perfect, and only runs the workflows as orchestrated by GitGitGadget's GitHub App as well as the scheduled workflows. Now that we changed the strategy in forked repositories from creating keepalive commits to first trying to grab a keepalive commit from the upstream repository, we need to increase the frequency of trying to do so because the `gitgitgadget` org's runners are unfortunately frequently very busy (the Git maintainer delights in pushing out dozens of topic branches simultaneously, each of which triggers CI builds with a combined runtime of over 8 hours...), which means that the `keepalive` workflow might run in the fork well before the upstream repository gets to creating the keepalive commit. So let's just run things twice a month instead of just once a month. Signed-off-by: Johannes Schindelin <[email protected]>
1 parent 9fe2a82 commit 36fe012

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

.github/workflows/keepalive.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ name: Keep scheduled workflows alive
22

33
on:
44
schedule:
5-
- cron: "23 19 17 * *" # 7:23pm on every 17th of the month
5+
- cron: "23 19 3,17 * *" # 7:23pm on every 3rd and 17th of the month
66
workflow_dispatch:
77

88
env:

0 commit comments

Comments
 (0)