Skip to content
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

Move the tflint, shfmt, shellcheck, and markdownlint to super-linter #9

Open
dcallao opened this issue Feb 24, 2023 · 1 comment
Open

Comments

@dcallao
Copy link
Contributor

dcallao commented Feb 24, 2023

Move the tflint, shfmt, shellcheck, and markdownlint to super-linter (that issue could possibly include--or be dependent on--adding tfsec support to super-linter).

@cprivitere
Copy link
Member

cprivitere commented Oct 1, 2024

We could also look into using the bespoke actions for most of these.

Either way, markdownlint is especially frustrating right now as vscode wants to use the javascript based markdownlint config format while our pre-commit github action uses the ruby based markdownlint config format, meaning your vscode will complain about issues we've disabled in the github side's config.

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

No branches or pull requests

2 participants