-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Markdown linting README.md #307
Conversation
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.
Thanks for the PR!
While the Markdown linting might look like a good enhancement at first, unlike .yaml
linter where issues should be actionable or .rst
linter for docs.stackstorm.com where the issue might lead to a broken template, or ansible-lint
which is based on the best practices, Markdown linter provides just a little value while bringing lots of noise for a single README.md.
README.md
Outdated
> [StackStorm](http://stackstorm.com/) is event-driven automation platform written in Python. | ||
With over [50+ integrations](https://github.com/StackStorm/st2contrib/tree/master/packs) like GitHub, Docker, Nagios, NewRelic, AWS, Ansible it allows you to wire together your existing infrastructure into complex Workflows with auto-remediation and many more. | ||
Aka IFTTT orchestration for Ops. | ||
|
||
> [StackStorm](http://stackstorm.com/) is event-driven automation platform | ||
> written in Python. | ||
|
||
With over [50+ integrations](https://github.com/StackStorm/st2contrib/tree/master/packs) | ||
like GitHub, Docker, Nagios, NewRelic, AWS, Ansible it allows you to wire | ||
together your existing infrastructure into complex Workflows with | ||
auto-remediation and many more. Aka IFTTT orchestration for Ops. |
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.
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.
Cool, I'll remove the CI and fix the problems in the README when I get a few.
Down to only line length warnings: ❯ mdl README.md
README.md:51: MD013 Line length
README.md:53: MD013 Line length
README.md:54: MD013 Line length
README.md:55: MD013 Line length
README.md:56: MD013 Line length
README.md:57: MD013 Line length
README.md:59: MD013 Line length
README.md:60: MD013 Line length
README.md:61: MD013 Line length
README.md:63: MD013 Line length
README.md:64: MD013 Line length
README.md:65: MD013 Line length
README.md:66: MD013 Line length
README.md:67: MD013 Line length
README.md:69: MD013 Line length
README.md:70: MD013 Line length
README.md:71: MD013 Line length
README.md:72: MD013 Line length
README.md:74: MD013 Line length
README.md:75: MD013 Line length
README.md:76: MD013 Line length
README.md:77: MD013 Line length
README.md:78: MD013 Line length
README.md:79: MD013 Line length
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md |
7e7a01e
to
31bd6d1
Compare
Hi @mamercad, we don't enforce the line length limit for Markdown files. To make the build green, you can update your working branch with the most recent upstream master. |
The linting problems were visual noise in my IDE, that's all. I'll rebase shortly. |
9deab64
to
f051dbd
Compare
If you'd like me to undo line length, just let me know. |
@mamercad Yes, please. |
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.
Thanks 👍
Fixes #306;
adding.markdownlint
to CI as well