Skip to content

Commit 01208b8

Browse files
committed
Spread out schedule workflow triggers
In order to catch breakage caused by external changes, the project's GitHub Actions workflows have a schedule event trigger. Previously, all the triggers were configured to trigger at the same time. It seems that this might cause spurious workflow run failures due to rate limiting or anti-DDoS systems. In order to avoid that, the triggers are configured to occur at various times.
1 parent b1590e2 commit 01208b8

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

.github/workflows/check-go-task.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,8 @@ on:
2323
- "**/go.sum"
2424
- "**.go"
2525
schedule:
26-
# Run every Tuesday at 8 AM UTC to catch breakage caused by changes to tools.
27-
- cron: "0 8 * * TUE"
26+
# Run periodically to catch breakage caused by external changes.
27+
- cron: "0 7 * * WED"
2828
workflow_dispatch:
2929
repository_dispatch:
3030

.github/workflows/test-go-integration-task.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,8 +31,8 @@ on:
3131
- "pyproject.toml"
3232
- "tests/**"
3333
schedule:
34-
# Run daily at 8 AM UTC to catch breakage resulting from changes to Arduino Lint.
35-
- cron: "0 8 * * *"
34+
# Run periodically to catch breakage caused by external changes.
35+
- cron: "0 10 * * WED"
3636
workflow_dispatch:
3737
inputs:
3838
arduino-lint-ref:

0 commit comments

Comments
 (0)