[GH-ISSUE #438] MD024: Allow hr separated sections to share titles/subtitles #366

Open
opened 2026-03-03 01:26:15 +03:00 by kerem · 5 comments
Owner

Originally created by @RonnyPfannschmidt on GitHub (Oct 6, 2021).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/438

when writing markdown presentations with markdown using hr as separator its sometimes helpful to repeat a larger title
followup to #437

## topic
### part 1
---

## topic
### part 2
-----

## topic b
### part 1
---
## topic b
### part 2

i have that pattern in presentations that have short code snippets followed by output snipped

Originally created by @RonnyPfannschmidt on GitHub (Oct 6, 2021). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/438 when writing markdown presentations with markdown using hr as separator its sometimes helpful to repeat a larger title followup to #437 ```markdown ## topic ### part 1 --- ## topic ### part 2 ----- ## topic b ### part 1 --- ## topic b ### part 2 ``` i have that pattern in presentations that have short code snippets followed by output snipped
Author
Owner

@DavidAnson commented on GitHub (Oct 6, 2021):

This feels pretty specific - why not turn off MD024 for this scenario?

<!-- gh-comment-id:936566576 --> @DavidAnson commented on GitHub (Oct 6, 2021): This feels pretty specific - why not turn off MD024 for this scenario?
Author
Owner

@RonnyPfannschmidt commented on GitHub (Oct 6, 2021):

It's what i currently do,

I do prefer to minimise the linter ignores per project

<!-- gh-comment-id:936703248 --> @RonnyPfannschmidt commented on GitHub (Oct 6, 2021): It's what i currently do, I do prefer to minimise the linter ignores per project
Author
Owner

@NudeNULL commented on GitHub (Mar 3, 2024):

I am voting it up as well, why showing a warning if it specifically adheres to the rules for changelogs
image

<!-- gh-comment-id:1975115232 --> @NudeNULL commented on GitHub (Mar 3, 2024): I am voting it up as well, why showing a warning if it specifically adheres to the rules for changelogs ![image](https://github.com/DavidAnson/markdownlint/assets/15786742/6cf6f4bd-035b-47fc-88a3-50e075508269)
Author
Owner

@DavidAnson commented on GitHub (Mar 3, 2024):

@NudeNULL, the changelog scenario is already supported via the siblings_only parameter: https://github.com/DavidAnson/markdownlint/blob/main/doc/md024.md

<!-- gh-comment-id:1975250482 --> @DavidAnson commented on GitHub (Mar 3, 2024): @NudeNULL, the changelog scenario is already supported via the `siblings_only` parameter: https://github.com/DavidAnson/markdownlint/blob/main/doc/md024.md
Author
Owner

@NudeNULL commented on GitHub (Mar 4, 2024):

Oh cool thanks! Thats very handy.

<!-- gh-comment-id:1975879421 --> @NudeNULL commented on GitHub (Mar 4, 2024): Oh cool thanks! Thats very handy.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/markdownlint#366
No description provided.