This repository has been archived by the owner on Nov 15, 2019. It is now read-only.
Add remark #10
Merged
Add remark #10
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is some infrastructure to keep our markdown files sanely formatted.
Remark is a linter for markdown files. And as this project is almost entirely markdown we should probably keep that all in check. This PR adds remark to the project and creates a CI build step to double check that the person submitting the changes has checked their work.
I used the default / recommended option here because I don't really care as long as we're all doing the same thing. The only rule that caught me by surprise was this 3 spaces after a list item which I've never done before.