GH Actions: add markdown linting and yaml linting #176
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.
GH Actions: add new check for consistency in markdown files
This new check uses the NPM MarkdownLint package via the NPM MarkdownLint-CLI2 package.
It executes a loose check for consistency and some common errors.
Some of the more annoying rules/rules which could impact display of markdown files on GitHub have been disabled.
All necessary configuration is contained in the
.markdownlint-cli2.yamlfile.To run locally, install via:
... and then run via:
Includes a problem matcher in the reusable workflow, which should allow for displaying the results inline in GitHub PR code review view.
Includes adding the config file to
.gitattributes.Includes adding
node_modulesto the.gitignorein case anyone would install these tools locally (to prevent them committing them).Refs:
Docs: tweak markdown for compliance with markdownlint
GH Actions: add new check with additional QA for markdown files
While MarkdownLint is absolutely great for finding formatting issues, Remark offers some additional "rules" which are useful, such as checking that links and link definitions match up, verifying all used links work and some additional formatting checks which markdownlint just doesn't offer.
An extensive effort has been made to prevent duplication of messages between the Markdownlint and the Remark check. This includes ensuring there are no conflicting rules.
The rule configuration is contained in the
.remarkrcfile.Files/directories to be ignored can be listed in the
.remarkignorefile which supports glob syntax, like.gitignore.Note:
.-prefixed files and directories are excluded by default. To include those in the scan, they have to be passed explicitly on the command-line.Refs:
Additional (external) plugins included:
Docs: fix various links
GH Actions: add Yamllint to QA basics
... to loosely safeguard valid and consistent yaml files.
Includes adding a configuration file which loosens up the
defaultruleset to a degree I'm comfortable with.Ref: https://yamllint.readthedocs.io/
Yaml: various tweaks for compliance with Yamllint and actionlint