Commit 74bb001
committed
Add schedule event triggers to GitHub Actions workflows
GitHub Actions workflows used to validate project content are configured to be triggered by any push or pull request
that modifies relevant files. These workflows rely on external resources such as the GitHub Actions infrastructure,
GitHub Actions actions, dependencies. Inevitably, breaking changes will occur in these resources, requiring adaptation
of the project infrastructure to fix.
If the workflow is only configured to run on changes to project files, breakage caused by external changes will only be
revealed by contributor activity. This results in confusion for the contributor who will assume the failing workflow run
was caused by the change they made. This results in inconvenience for the maintainer who must explain the situation to
the contributor and do without the benefit of the automated validation of the contribution.
For this reason, it is best practices to always configure such GitHub Actions workflows to also be triggered on a
schedule. This allows breakage to be detected and resolved before it impacts contributions.1 parent 18c6507 commit 74bb001
File tree
3 files changed
+9
-0
lines changed- .github/workflows
3 files changed
+9
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
25 | 25 | | |
26 | 26 | | |
27 | 27 | | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
28 | 31 | | |
29 | 32 | | |
30 | 33 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
195 | 195 | | |
196 | 196 | | |
197 | 197 | | |
| 198 | + | |
| 199 | + | |
| 200 | + | |
198 | 201 | | |
199 | 202 | | |
200 | 203 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
39 | 39 | | |
40 | 40 | | |
41 | 41 | | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
42 | 45 | | |
43 | 46 | | |
44 | 47 | | |
| |||
0 commit comments