Add markdownlint to ensure consistent formatting #14
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.
I've seen too many places where markdown becomes hard to read over time due to different peoples preferences wrt. formatting and style. Starting out with a unified formatting strategy can lessen this problem.
I've added a GitHub Action for validating all markdown in the repo and a small
.markdownlint.yaml
config file with all defaults except for disabling line length requirements. We can discuss further changes from there.