mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-26 01:36:03 +03:00
[GH-ISSUE #607] Add mdn/content repo to smoke tests #475
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#475
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 @nschonni on GitHub (Oct 14, 2022).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/607
The repo now has Markdownlint enabled https://github.com/mdn/content and is a fair sized repo with some unique things. Downsides are that the custom generator https://github.com/mdn/yari does include some template extensions that aren't CommonMark complaint, and neither is the anchor linking schema.
The parallel i18n repo https://github.com/mdn/translated-content may also be an interesting one later, but the full Markdownlint CI hasn't landed yet.
@DavidAnson commented on GitHub (Dec 15, 2022):
@nschonni, FYI that I claim the 3 violations newly reported in that repo for
nextbranch are legitimate issues (two have extra "()" wrappers, one a trailing ")"):github.com/DavidAnson/markdownlint@d352d4ece1 (diff-04131531c5)@DavidAnson commented on GitHub (Dec 15, 2022):
(To be fair, I fixed the other things this turned up because they were legitimate bugs in MY code. :) This was a good addition!)
@nschonni commented on GitHub (Dec 15, 2022):
Not sure if I caught them all, but submitted https://github.com/mdn/content/pull/22991
The repo has an auto-cleanup job and a commit hook, so likely something malformed that had a bad fix before
@DavidAnson commented on GitHub (Dec 15, 2022):
Looks good!
@nschonni commented on GitHub (Dec 16, 2022):
Upstream PR landed, so you can probably clean up the ignores again
@nschonni commented on GitHub (Dec 16, 2022):
And I guess this can be closed if you've added it now, unless you want to keep it open to track the
translaterepo too@DavidAnson commented on GitHub (Dec 16, 2022):
This issue will be closed automatically when I merge next branch into main.