mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 09:16:02 +03:00
[GH-ISSUE #1882] MD024/no-duplicate-heading siblings_only: true has no affect #2616
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#2616
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @seanthegeek on GitHub (Dec 4, 2025).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1882
I created the following
.markdownlint.ymlfile to enable thesimlings_onlyoption in MD024/no-duplicate-headingWhen I create a changelog markdown file like in the example:
markdownlintstill raises a warning:I know that the
.markdownlint.ymlis being read, because the warning goes away if I disable the rule completely.@DavidAnson commented on GitHub (Dec 4, 2025):
I can only superficially check this from my phone, but it seems to be working as expected, so I suspect the issue is something to do with the configuration you're providing. I'd start by making sure that YAML file is being parsed successfully.
https://dlaa.me/markdownlint/#%25m%23%20Change%20log%0A%0A%23%23%201.0.0%0A%0A%23%23%23%20Features%0A%0A%23%23%202.0.0%0A%0A%23%23%23%20Features%0A%0A%3C!--%20markdownlint-configure-file%20%7B%0A%20%20%22no-duplicate-heading%22%3A%20%7B%0A%20%20%20%20%22siblings_only%22%3A%20true%0A%20%20%7D%0A%7D%20--%3E%0A
@seanthegeek commented on GitHub (Dec 4, 2025):
It might be an issue with the implantation in Visual Studio Code then. I've tried both JSON and YANL config files with the same result.
@DavidAnson commented on GitHub (Dec 5, 2025):
Here's a repository/branch containing exact copies of the two files you provide above. You can clone and open the folder in VS Code with the markdownlint extension to confirm that no violations are reported.
https://github.com/DavidAnson/playground/tree/markdownlint-issue-1882
Please feel free to PR a change to that repository to demonstrate the problem you're seeing.
@seanthegeek commented on GitHub (Dec 5, 2025):
I'm an idiot. I should not open issues with little sleep.
github.com/domainaware/checkdmarc@f550117e7d