-
Notifications
You must be signed in to change notification settings - Fork 834
fix(docs): Fix Markdown validation #21808
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
Merged
agneszitte
merged 2 commits into
master
from
dev/jonpryor/jonp-fix-platform-status-inline-indentation
Nov 11, 2025
Merged
fix(docs): Fix Markdown validation #21808
agneszitte
merged 2 commits into
master
from
dev/jonpryor/jonp-fix-platform-status-inline-indentation
Nov 11, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CI is broken; the "Run Markdown Linter" job fails with: doc/articles/includes/uno-platform-status-inline.md:5 MD001/heading-increment Heading levels should only increment by one level at a time [Expected: h2; Actual: h3] doc/articles/includes/uno-platform-status-inline.md:5 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### [**Visual Studio 2022**](#tab/vswints)"] doc/articles/includes/uno-platform-status-inline.md:8 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### [**Visual Studio Code**](#tab/vscodets)"] doc/articles/includes/uno-platform-status-inline.md:11 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### [**Rider**](#tab/riderts)"] Replace `###` with `##` on the indicated lines to appease the linter.
jeromelaban
approved these changes
Nov 11, 2025
Contributor
Author
|
Seemingly broken by: https://github.com/unoplatform/uno/pull/21800/files#r2515732471 |
carldebilly
approved these changes
Nov 11, 2025
Contributor
|
|
Contributor
|
@Mergifyio backport release/stable/6.4 |
Contributor
✅ Backports have been createdDetails
|
dr1rrb
approved these changes
Nov 11, 2025
5 tasks
agneszitte
added a commit
that referenced
this pull request
Nov 11, 2025
…6.4/pr-21808 fix(docs): Fix Markdown validation (backport #21808)
Contributor
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-21808/docs/index.html |
agneszitte
added a commit
that referenced
this pull request
Nov 12, 2025
mergify bot
pushed a commit
that referenced
this pull request
Nov 12, 2025
… fixes) (cherry picked from commit a1f877b)
agneszitte
added a commit
that referenced
this pull request
Nov 12, 2025
…markdownfixes) (backport #21815)"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CI is broken; the "Run Markdown Linter" job fails with:
Replace
###with##on the indicated lines to appease the linter.GitHub Issue: closes #
PR Type:
What is the current behavior? 🤔
What is the new behavior? 🚀
PR Checklist ✅
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Runresults.Other information ℹ️