CI: run checks on a schedule and allow workflow_dispatch #90
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The failed CI job is unrelated to this PR and should be fixed in #89 (which is also what triggered this change in the first place 😉 ). |
Running checks on a schedule makes sense for our `ruff` lints and our `codespell` spell checks, because these tools learn new lints/typo fixes every then and now. Without periodic job runs these new lints/typo fixes will only surface when jobs for the next pull request fail for unrelated reasons. The execution time of the scheduled job is chosen somewhat arbitrarily. While at it also enable workflow_dispatch as a trigger, which can be used to run the jobs manually. Signed-off-by: Leonard Göhrs <l.goehrs@pengutronix.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Running checks on a schedule makes sense for our
rufflints and ourcodespellspell checks, because these tools learn new lints/typo fixes every then and now.Without periodic job runs these new lints/typo fixes will only surface when jobs for the next pull request fail for unrelated reasons.
The execution time of the scheduled job is chosen somewhat arbitrarily.
While at it also enable workflow_dispatch as a trigger, which can be used to run the jobs manually.