Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Markdownlint configuration #133

Merged
merged 1 commit into from
Jan 10, 2019
Merged

Conversation

jonasbn
Copy link
Collaborator

@jonasbn jonasbn commented Jan 9, 2019

Hi @naokazuterada

I have added a basic Markdownlint configuration and adjusted a few Markdown issues pointed out by Markdownlint.

I am primarily using the plugin for VSCode, but there is both a Node and a Ruby implementation.

A marvelous tool to catch basic Markdown issues and helping in following best practices.

@codecov
Copy link

codecov bot commented Jan 9, 2019

Codecov Report

Merging #133 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #133   +/-   ##
=======================================
  Coverage   90.44%   90.44%           
=======================================
  Files           8        8           
  Lines         408      408           
=======================================
  Hits          369      369           
  Misses         39       39

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8ac53f9...f0a2580. Read the comment docs.

@naokazuterada naokazuterada merged commit 96f1f75 into master Jan 10, 2019
@naokazuterada
Copy link
Owner

@jonasbn Thanks!!

@naokazuterada naokazuterada deleted the markdownlint-configuration branch April 16, 2019 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants