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

Add markdown linter and fix linter errors #117

Merged
merged 4 commits into from
Jan 20, 2025
Merged

Add markdown linter and fix linter errors #117

merged 4 commits into from
Jan 20, 2025

Conversation

michaelin
Copy link
Contributor

No description provided.

@michaelin michaelin force-pushed the update-docs branch 5 times, most recently from f8105fa to afa4c16 Compare January 20, 2025 14:30
This adds a new GitHub Action to lint all markdown files in the project.

A configuration file limits line lengths to 100 charactes (default is 80) and excludes code blocks
and tables from this limit. It also allows the <details> and <summary> tags, since there are no
good alternatives.

Linting is disabled for anything in `/old` and `/scenarios`.

Finally vscode will suggest adding the markdownlint extension when opening the project. This will
help vscode users to get linting warnings _before_ committing.
This fixes the existing markdownlint errors that are _not_ related to line length. Those will be dealt with separately, since word wrapping may be a controversial subject.
@michaelin michaelin marked this pull request as ready for review January 20, 2025 14:40
@michaelin michaelin merged commit 1e7fca7 into master Jan 20, 2025
8 checks passed
@michaelin michaelin deleted the update-docs branch January 20, 2025 14:42
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.

1 participant