-
Notifications
You must be signed in to change notification settings - Fork 8
/
.markdownlint.yml
83 lines (72 loc) · 3.01 KB
/
.markdownlint.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
# Copyright 2023 The OpenXLA Authors
#
# Licensed under the Apache License v2.0 with LLVM Exceptions.
# See https://llvm.org/LICENSE.txt for license information.
# SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
# markdownlint-cli configuration file.
# https://github.com/igorshubovych/markdownlint-cli
# https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md
# Enable all markdownlint rules by default
default: true
# List formatting:
#
# 1. Lists must have a blank line before AND after the list.
# 2. Lists start aligned to the left (do not indent the top level list items).
# NOTE: markdownlint currently checks indentation for unordered lists only.
# Please manually verify that your ordered lists are not indented.
# See https://github.com/DavidAnson/markdownlint/issues/138.
# 3. You may use one or zero blank lines between list items.
# 4. Nested list items should be indented 4 spaces.
# 5. In multiline list items, subsequent lines are indented to align with the
# first character of the first line. This is not checked automatically, so
# we're documenting this convention for consistency.
#
# Examples:
#
# * This is a list item that has multiple
# lines and each line aligns with the text from the first line.
# * This is a nested list, indented 4 spaces so it stands out.
ul-indent:
indent: 4
# Allow inconsistent unordered list style so we can use both standard ULs
# and the non-standard task lists (`- [ ]` and `- [x]`)
ul-style: false
# Allow inconsistent code block style so we can use non-standard content tabs
# https://squidfunk.github.io/mkdocs-material/reference/content-tabs/#grouping-code-blocks
code-block-style: false
# Limit to 80-char line length, except for tables and code blocks
line-length:
line_length: 80
tables: false
code_blocks: false
# Allow inline HTML
no-inline-html: false
# Allow dupe heading names only if they're not siblings
no-duplicate-heading:
siblings_only: true
# Allow images w/o alt-text
no-alt-text: false
# Allow first line to be something other than a heading
# (we use this for date/author in blog posts)
first-line-heading: false
# Link style:
# Markdown links can normally provide link destinations elsewhere and
# simply reference those destinations by a label, e.g.
#
# <!-- Middle of file -->
# [text][label]
#
# <!-- Bottom of file -->
# [label]: https://example.com/label
#
# The 'reference-links-images' and 'link-image-reference-definitions' rules
# can (respectively) help ensure that all referenced labels exist and that no
# labels are orphaned. However, markdownlint does not recognize link
# references in content tabs so it reports false positive errors for "unused"
# link references. Because we can't reliably lint such references, we
# recommend _not using that style of linking at all_.
#
# There is no rule (yet?) to enforce inline links over reference links, but
# https://github.com/DavidAnson/markdownlint/issues/40 may add one.
#
# TLDR: Add your links inline, as in [text](www.example.com).