ci: Add GitHub workflow to run code linting checks daily, on push, and on pull request. #11
Conversation
This file contains hidden or 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
davidlion
requested changes
Jan 23, 2025
davidlion
changed the title
davidlion
approved these changes
Jan 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
With the first set of linters added (for YAML files), automated GitHub workflow to lint files can now be set up.
This is important before we add more configuration YAML files to the project.
The linting workflow file follows the current practice in clp, with three differences:
clp-linttocode-linting-checks, which is more generic.permissions: {}, which disables all token permissions. This enhances security for workflows where no repository interactions are required.Log tool versionsfor better debuggability.For details, see spider.
Validation performed