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

Clean up MegaLinter errors and warnings #137

Closed
wesley-dean-gsa opened this issue Aug 2, 2024 · 2 comments · Fixed by #134
Closed

Clean up MegaLinter errors and warnings #137

wesley-dean-gsa opened this issue Aug 2, 2024 · 2 comments · Fixed by #134
Assignees

Comments

@wesley-dean-gsa
Copy link
Contributor

MegaLinter found a bunch of things that need to be tidied up, some of which can be done automatically and some of which (e.g., security ones) may involve a little more manual intervention.

@wesley-dean-gsa wesley-dean-gsa added this to the Technical Debt milestone Aug 2, 2024
@wesley-dean-gsa wesley-dean-gsa self-assigned this Aug 2, 2024
@wesley-dean-gsa wesley-dean-gsa linked a pull request Aug 2, 2024 that will close this issue
@wesley-dean-gsa
Copy link
Contributor Author

The PR (#134) is more current with regards to updates on the progress for this.

tl;dr: we're mostly done with most of the fixes. There are just a few left to tidy up and we can close this out.

@wesley-dean-gsa
Copy link
Contributor Author

The v8r linter error involved a missing field in the tool's validation schema; this was documented in tcort/markdown-link-check#355 and resolved in SchemaStore/schemastore#3972. If MegaLinter runs again, the JSON_V8R checks that were failing for .markdown-link-check.json will now pass.

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

Successfully merging a pull request may close this issue.

1 participant