-
Notifications
You must be signed in to change notification settings - Fork 147
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
Add linters to CI #883
base: main
Are you sure you want to change the base?
Add linters to CI #883
Conversation
Signed-off-by: Matthias Pichler <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good! I believe you're still working on GHA. 👍
It might actually be that super-linter is looking for the config files on the main branch and therefore can't find it 🤔 |
Maybe we can open another PR and then rebase this one? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks ❤️
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Please specify parts of this PR update:
Discussion or Issue link:
What this PR does:
I added the super-linter action to lint & format yaml and markdown files.
I also updated the contributing guide to use the same packages as super-lint. (Specifically markdown-lint instead of mdl)
And I formated and linted all files to make them compliant.
Additional information: