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 markdownlint to ensure consistent formatting #14

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

michaelin
Copy link

I've seen too many places where markdown becomes hard to read over time due to different peoples preferences wrt. formatting and style. Starting out with a unified formatting strategy can lessen this problem.

I've added a GitHub Action for validating all markdown in the repo and a small .markdownlint.yaml config file with all defaults except for disabling line length requirements. We can discuss further changes from there.

A new linting job has been added to the PR workflow,
and both workflows now triggers on changes to themselves as well
as all markdown files in the root directory and Hugo dirs.
All default MarkdownLint rules are enabled except for MD013/line-length. This rule is often debated, and its value is dependent on your editors word wrap features and configuration.
@michaelin michaelin marked this pull request as ready for review February 21, 2025 13:58
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