-
Notifications
You must be signed in to change notification settings - Fork 115
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
Add markdownlint #2662
Add markdownlint #2662
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2662 +/- ##
=======================================
Coverage 63.09% 63.09%
=======================================
Files 365 365
Lines 34587 34587
=======================================
+ Hits 21822 21823 +1
+ Misses 10048 10047 -1
Partials 2717 2717
Continue to review full report at Codecov.
|
line-length: | ||
# Line length checking is not strict by default. | ||
strict: true | ||
line_length: 80 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any specific reason for 80?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nothing in particular, 80 is something I'm most used to.
5836ec2
to
795377e
Compare
795377e
to
005ddb3
Compare
Add Lint Markdown files and Lint Change Log fragments steps to ci-lint GitHub Actions workflow.
It is more familiar to developers and prevents confusion between requiring a Change Log fragment's subject line to end with period and requiring a Git commit message's subject line not to end with a period.
005ddb3
to
546dfaf
Compare
Closes #2572.
TODO:
gitlint
to lint the Change Log fragments.