Skip to content
Markdown Checks

ci: add markdown lint and link validation #1

Sign in to view logs

ci: add markdown lint and link validation

ci: add markdown lint and link validation #1

Triggered via pull request April 13, 2026 02:19
@FrancesCoronelFrancesCoronel
opened #20
ci/markdown-checks
Status Failure
Total duration 1m 3s
Artifacts –

markdown-checks.yml

on: pull_request
Lint
3s
Lint
Link Check
1m 0s
Link Check
Fit to window
Zoom out
Zoom in

Annotations

6 errors, 2 warnings, and 1 notice
Lint
Failed with exit code: 1
First line in a file should be a top-level heading: README.md#L1
README.md:1 MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "![DiversifyMe](https://i.imgur..."] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md041.md
First line in a file should be a top-level heading: CONTRIBUTING.md#L1
CONTRIBUTING.md:1 MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "## Contributing"] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md041.md
First line in a file should be a top-level heading: .github/PULL_REQUEST_TEMPLATE.md#L1
.github/PULL_REQUEST_TEMPLATE.md:1 MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "Insert description of PR here"] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md041.md
First line in a file should be a top-level heading: .github/ISSUE_TEMPLATE.md#L1
.github/ISSUE_TEMPLATE.md:1 MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "Insert description of issue he..."] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md041.md
Link Check
Process completed with exit code 2.
Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, DavidAnson/markdownlint-cli2-action@v16. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Link Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Link Check