[GH-ISSUE #1419] Allow Consecutive GitHub Alerts #680

New issue

Closed

opened 2026-03-03 01:29:00 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 01:29:00 +03:00

Owner

Originally created by @gabeseltzer on GitHub (Nov 15, 2024).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1419

GitHub uses the following syntax for "Alerts":

> [!NOTE]
> Useful information that users should know, even when skimming content.

If you put two alerts consecutively like this, you get a warning about: MD028/no-blanks-blockquote: Blank line inside blockquote

> [!NOTE]
> my first note.

> [!NOTE]
> A second, consecutive note...

Can we change the parsing for the rule so that it recognizes the kinds of alerts and allows spaces between them?

Originally created by @gabeseltzer on GitHub (Nov 15, 2024). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1419 GitHub uses the following syntax for ["Alerts"](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts): ```markdown > [!NOTE] > Useful information that users should know, even when skimming content. ``` If you put two alerts consecutively like this, you get a warning about: `MD028/no-blanks-blockquote: Blank line inside blockquote` ```markdown > [!NOTE] > my first note. > [!NOTE] > A second, consecutive note... ``` Can we change the parsing for the rule so that it recognizes the kinds of alerts and allows spaces between them?

kerem

2026-03-03 01:29:00 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-03 01:29:02 +03:00

Author

Owner

@DavidAnson commented on GitHub (Nov 16, 2024):

The rule documentation explains that this scenario is reported as a violation because some parsers combine consecutive blockquotes into one. That is not what the CommonMark specification says to do and it's not what GitHub does for blockquotes, but it can be a problem. I don't think this situation is unique to GitHub Alerts and I'd recommend disabling the rule if you're only authoring for GitHub.

https://github.com/DavidAnson/markdownlint/blob/main/doc/md028.md

@DavidAnson commented on GitHub (Nov 16, 2024): The rule documentation explains that this scenario is reported as a violation because some parsers combine consecutive blockquotes into one. That is not what the CommonMark specification says to do and it's not what GitHub does for blockquotes, but it can be a problem. I don't think this situation is unique to GitHub Alerts and I'd recommend disabling the rule if you're only authoring for GitHub. https://github.com/DavidAnson/markdownlint/blob/main/doc/md028.md

kerem referenced this issue

2026-03-03 02:01:14 +03:00

[PR #680] [CLOSED] docs: add ol_ to list-marker-space Prettier example #955

kerem referenced this issue

2026-03-07 20:10:39 +03:00

[PR #680] [CLOSED] docs: add ol_ to list-marker-space Prettier example #2806