Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 22, 2026

The markdown linter workflow exists but isn't catching violations like MD001 (heading increment). Three files had <!-- markdownlint-disable --> at the top, globally disabling all rules.

Changes

  • Removed <!-- markdownlint-disable --> from README.md, src/devices/README.md, and src/devices/Device-Index.md
  • Added MD012, MD041, MD060 to .markdownlint.json config to suppress pre-existing violations in those specific rules

The linter now catches violations while allowing intentional formatting choices (badges before H1, table styles, etc).

Original prompt

This section details on the original issue you should resolve

<issue_title>Markdown linter is not working</issue_title>
<issue_description>See #2467
This should have shown MD001</issue_description>

Comments on the Issue (you are @copilot in this section)


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Microsoft Reviewers: Open in CodeFlow

Co-authored-by: krwq <660048+krwq@users.noreply.github.com>
@dotnet-policy-service dotnet-policy-service bot added the area-device-bindings Device Bindings for audio, sensor, motor, and display hardware that can used with System.Device.Gpio label Jan 22, 2026
Copilot AI changed the title [WIP] Fix markdown linter not working Fix markdown linter not catching violations Jan 22, 2026
Copilot AI requested a review from krwq January 22, 2026 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-device-bindings Device Bindings for audio, sensor, motor, and display hardware that can used with System.Device.Gpio

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Markdown linter is not working

2 participants