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 added husky to run the markdownlint check as a pre-commit hook.
I've also added lint-staged, which does a couple of things for us:
*.md
files have been changed.Fixes #741
Here's what it looks like if you try to commit a file with a failing markdown check:
Here's what it looks like if there's no problems:
Here's what it looks like if no files that need linting have been changed:
@tomkerkhove if you want to try this out, just pull this branch, run
npm install
, make a change to a markdown file that causes an error and make a commit.