Skip to content

ci: also run jobs on a schedule #73

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

Merged
merged 1 commit into from
Jul 1, 2024

Conversation

hnez
Copy link
Member

@hnez hnez commented Jun 28, 2024

We have been bitten before by upstream codespell or cargo clippy adding new checks in times of low activity on the repo, resulting in the next pull requests to fail.

Make sure we notice such changes early by running the jobs on a schedule every then and now.
The scheduled time of 20:48 UTC every thursday was chosen by fair dice roll.

TODO before merging:

@hnez hnez requested a review from Emantor June 28, 2024 09:24
@hnez hnez force-pushed the ci-schedule branch 2 times, most recently from c9eb9b5 to da88e91 Compare June 28, 2024 09:31
We have been bitten before by `codespell` or `cargo clippy` adding new
checks in times of low activity on the repo, resulting in the next
pull requests to fail.

Make sure we notice such changes early by running the jobs on a schedule
every then and now.
The scheduled time of 20:48 UTC every thursdays was chosen by fair
dice roll.

Signed-off-by: Leonard Göhrs <[email protected]>
@SmithChart SmithChart merged commit 1f2145c into linux-automation:main Jul 1, 2024
14 checks passed
@hnez hnez deleted the ci-schedule branch July 1, 2024 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants