Skip to content

Validate markdown files - #74

Merged
paulineribeyre merged 2 commits into
masterfrom
feat/lint-md
Oct 23, 2023
Merged

Validate markdown files#74
paulineribeyre merged 2 commits into
masterfrom
feat/lint-md

Conversation

@paulineribeyre

@paulineribeyre paulineribeyre commented Oct 20, 2023

Copy link
Copy Markdown
Collaborator

Complains about bad syntax (but we can disable rules we don't care about) and about dead links.
The config is centralized here so that we use consistent style across repos.

Uses https://github.com/marketplace/actions/markdown-linting-action and https://github.com/marketplace/actions/markdown-link-check

Surround a link with <!-- markdown-link-check-disable --> and <!-- markdown-link-check-enable --> to skip link validation

New Features

  • Reusable workflow for markdown file validation

Avantol13
Avantol13 previously approved these changes Oct 23, 2023
- name: Set up config files
run: |
wget https://raw.githubusercontent.com/uc-cdis/.github/feat/lint-md/.github/workflows/validate_markdown_lint.jsonc -P .github/workflows/
wget https://raw.githubusercontent.com/uc-cdis/.github/feat/lint-md/.github/workflows/validate_markdown_links.json -P .github/workflows/

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pulling these here and running the lint right after in this workflow means that repos don't have the option of overriding or modifyig the config. In this case that's probably fine, but like for Super Lint b/c there's so many linters and probably different repos may want diff standards at first, I was trying to build in some flexibility to override the defaults. All that said, for the markdown linting I'm happy forcing the global config

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes i didn't have time to add configuration on friday, and i thought it'd be fine to merge it as-is and add configuration later if needed. plus this way all the repos are consistent

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, agreed

@paulineribeyre
paulineribeyre merged commit aa7ee3f into master Oct 23, 2023
@paulineribeyre
paulineribeyre deleted the feat/lint-md branch October 23, 2023 16:12
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.

2 participants