[GH-ISSUE #68] Add rule(s) to enforce certain link rules #55

New issue

Open

opened 2026-03-03 01:23:22 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 01:23:22 +03:00

Owner

Originally created by @braebot on GitHub (Jul 22, 2017).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/68

Add rules to detect and error when found:

No http links,
No links include text from a set of given regexes,
No relative links, such as ../path, path. Only allow absolute links, such as /path.

Note: this is similar to those that would be found when crawling a site. However, it is best when caught earlier in the process with markdownlint.

Originally created by @braebot on GitHub (Jul 22, 2017). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/68 Add rules to detect and error when found: 1. No `http` links, 2. No links include text from a set of given regexes, 3. No relative links, such as `../path`, `path`. Only allow absolute links, such as `/path`. Note: this is similar to those that would be found when crawling a site. However, it is best when caught earlier in the process with markdownlint.

kerem added the

new rule

label

2026-03-03 01:23:22 +03:00

kerem commented

2026-03-03 01:23:22 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jul 22, 2017):

Based on your scenarios, a single rule that runs a user-configurable RegExp against the link destination seems sufficient.

@DavidAnson commented on GitHub (Jul 22, 2017): Based on your scenarios, a single rule that runs a user-configurable RegExp against the link destination seems sufficient.

kerem commented

2026-03-03 01:23:22 +03:00

Author

Owner

@braebot commented on GitHub (Jul 22, 2017):

Yes, that would be sufficient!

@braebot commented on GitHub (Jul 22, 2017): Yes, that would be sufficient!

kerem commented

2026-03-03 01:23:23 +03:00

Author

Owner

@sanmai-NL commented on GitHub (Nov 20, 2020):