René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Create a `max-heading-level` rule","articleBody":"When Markdown content is rendered on GitHub, it is rendered into the context of a webpage. This means there is already an external heading structure to contend with.\n\nIn issue and PR comments, the maximum heading level that should be used is 3 (`###`). In files in Code View, the maximum should be 2 (`##`).\n\nI think it's debatable whether Markdown files should be written with their intended viewing location in mind - Markdown is supposed to be a rendering-agnostic markup format. But comments should probably always be written like this. So I think it would be useful to make a new rule available, but **disable it by default**.\n\nI propose we make this generic, allowing the linter to customize the heading level for the situation. For example, the following configuration would be for comments on github.com:\n\n```js\n{\n    \"max-heading-level\": {\n        \"level\": 3\n    }\n}\n```\n\nRelated:\n\n- https://github.com/iansan5653/github-markdown-a11y-extension/issues/14","author":{"url":"https://github.com/iansan5653","@type":"Person","name":"iansan5653"},"datePublished":"2023-10-06T15:36:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/86/markdownlint-github/issues/86"}