Open dcallao opened 1 year ago
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.
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).