Conversation
ignores template pages--these shouldn't be edited and were designed for ease-of-use ignores mkdocs.yaml avoid rules that don't work in some locations (e.g., need HTML for table formatting)
linter has consistency within a file, not as much across
Add new settings and linting instructions Add note that local linting is optional
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Applied the linter to the repo and adjusted the rules where needed:
markdownlint(and VS Code), though it renders properly on the site.For the record, the linter has consistency within a file, not as much across files (e.g.,
-vs*as a bullet point). We should now be at the point where an action could be added without causing a major headache.