Repository navigation
Lint the Markdown files in CI - #714
Merged
Merged
Conversation
It mirrors the config we use in CIDER.
Disable the line-length and duplicate-heading rules that don't fit a changelog and drop a stray double blank line.
Give the demo images alt text, pad the table delimiter rows, wrap the long lines and name the changelog link.
It lints every Markdown file with the config in .markdownlint-cli2.yaml.
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
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.
Adds the markdownlint config CIDER uses and a CI job that runs it over every Markdown file. The README needed alt text for its demo images and a few wrapped lines to pass.