[GH-ISSUE #102] MD024 triggers on same inner headers inside different top-level headers #1933

New issue

Closed

opened 2026-03-07 20:02:54 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 20:02:54 +03:00

Owner

Originally created by @KillyMXI on GitHub (Jan 7, 2018).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/102

# Issue A

## Solution

# Issue B

## Solution

-- looks totally fine for me and I don't want it to be triggered.

Originally created by @KillyMXI on GitHub (Jan 7, 2018). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/102 ``` # Issue A ## Solution # Issue B ## Solution ``` -- looks totally fine for me and I don't want it to be triggered.

kerem

2026-03-07 20:02:54 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-07 20:02:56 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jan 7, 2018):

That’s correct behavior for MD024 - the rationale explains why: https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md024

You might want to disable MD024 for that file or for your project if you don’t agree with the rule.

You might also look into MD043 as an alternate way to enforce header structure: https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md043

Hope this helps!

@DavidAnson commented on GitHub (Jan 7, 2018): That’s correct behavior for MD024 - the rationale explains why: https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md024 You might want to disable MD024 for that file or for your project if you don’t agree with the rule. You might also look into MD043 as an alternate way to enforce header structure: https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md043 Hope this helps!

kerem commented

2026-03-07 20:02:56 +03:00

Author

Owner

@KillyMXI commented on GitHub (Jan 7, 2018):

So it's just a workaround thing for some parsers.
I missed that line.

Disabling it is a way to go for me then.

@KillyMXI commented on GitHub (Jan 7, 2018): So it's just a workaround thing for some parsers. I missed that line. Disabling it is a way to go for me then.

kerem referenced this issue

2026-03-07 20:09:31 +03:00

[GH-ISSUE #1933] gunna #2630