[GH-ISSUE #1129] MD029: Ordered list with Note block #617

New issue

Closed

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

kerem commented

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

Owner

Originally created by @SerTetora on GitHub (Feb 15, 2024).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1129

I encountered an issue with Markdown rendering where I have an ordered list in my Markdown file, separated by a note block. Despite the correct content, it generates the MD029 warning.

Original:

1. Fist item:

> [!NOTE]
> Some note

2. second item

It is rendered as

Fist item:

Note

Some note

second item

However, this setup triggers the MD029 warning. According to MD029, a solution is proposed to indent the code block so it becomes part of the preceding list item as intended:

1. Fist item:

    > [!NOTE]
    > Some note

2. second item

However, after applying this solution, the note is rendered incorrectly:

Fist item:

Note

Some note
second item

Originally created by @SerTetora on GitHub (Feb 15, 2024). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1129 I encountered an issue with Markdown rendering where I have an ordered list in my Markdown file, separated by a note block. Despite the correct content, it generates the MD029 warning. Original: ``` 1. Fist item: > [!NOTE] > Some note 2. second item ``` It is rendered as 1. Fist item: > [!NOTE] > Some note 2. second item However, this setup triggers the MD029 warning. According to [MD029](https://github.com/DavidAnson/markdownlint/blob/v0.33.0/doc/md029.md), a solution is proposed to indent the code block so it becomes part of the preceding list item as intended: ``` 1. Fist item: > [!NOTE] > Some note 2. second item ``` However, after applying this solution, the note is rendered incorrectly: 1. Fist item: > [!NOTE] > Some note 2. second item

kerem

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

closed this issue
added the
question
label

kerem commented

2026-03-03 01:28:30 +03:00

Author

Owner

@DavidAnson commented on GitHub (Feb 15, 2024):

You'll probably want to suppress that warning in this case. It seems that GitHub only recognizes notes when they are fully left-aligned. But when that's done, it creates two separate lists and the second list begins with 2 instead of 1, so the markdownlint warning is correct. GitHub allows you to start a list with a different number than 1 which is why this looks OK rendered.

@DavidAnson commented on GitHub (Feb 15, 2024): You'll probably want to suppress that warning in this case. It seems that GitHub only recognizes notes when they are fully left-aligned. But when that's done, it creates two separate lists and the second list begins with 2 instead of 1, so the markdownlint warning is correct. GitHub allows you to start a list with a different number than 1 which is why this looks OK rendered.

kerem referenced this issue

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

[PR #617] [MERGED] Bump eslint from 8.25.0 to 8.26.0 #921

kerem referenced this issue

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

[PR #617] [MERGED] Bump eslint from 8.25.0 to 8.26.0 #2771