Skip to content

Cherrypick out linter #113

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

vpetersson
Copy link
Contributor

Cherry pick out Markdown linter without actually running it.

@vpetersson vpetersson requested review from oej and madpah as code owners April 16, 2025 14:21
Signed-off-by: Viktor Petersson <self@vpetersson.com>
@madpah
Copy link
Collaborator

madpah commented Apr 17, 2025

@vpetersson - any reason you have chosen not to use an existing GitHub Action for this?

@vpetersson
Copy link
Contributor Author

vpetersson commented Apr 17, 2025

@madpah I've found Super Linter to be super slow (and bloated) in the past. I just copied this from other pipelines where I've added this setup. We could definitely add an upstream Action, but it was just a few lines so i figured it was easier to implement.

However, if you feel strongly that we should use an existing action, I can change it.

@madpah
Copy link
Collaborator

madpah commented Apr 17, 2025

No strong opinion - just having the chat 😉

@vpetersson
Copy link
Contributor Author

All good, mate! Yeah I usually try to use (well maintained) Action modules too, but haven't found a good one for this.

Also, note that the tests are failing because I didn't run it. @oej asked me to not apply the linting in this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants