diff options
| author |  Ash Holland <ash@sorrel.sh> | 2020-05-02 14:15:43 +0100 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2020-05-02 18:04:12 -0700 |
| commit | 09dad9256a32affc4a3bc0cf1fa45d5fa6f51231 (patch) | |
| tree | 077894ab6bd3dc84f7c030d2aec50c0847311d61 /t/t4018 | |
| parent | The third batch (diff) | |
| download | tgif-09dad9256a32affc4a3bc0cf1fa45d5fa6f51231.tar.xz | |
userdiff: support Markdown
It's typical to find Markdown documentation alongside source code, and
having better context for documentation changes is useful; see also
commit 69f9c87d4 (userdiff: add support for Fountain documents,
2015-07-21).
The pattern is based on the CommonMark specification 0.29, section 4.2
<https://spec.commonmark.org/> but doesn't match empty headings, as
seeing them in a hunk header is unlikely to be useful.
Only ATX headings are supported, as detecting setext headings would
require printing the line before a pattern matches, or matching a
multiline pattern. The word-diff pattern is the same as the pattern for
HTML, because many Markdown parsers accept inline HTML.
Signed-off-by: Ash Holland <ash@sorrel.sh>
Acked-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4018')
| -rw-r--r-- | t/t4018/markdown-heading-indented | 6 | ||||
| -rw-r--r-- | t/t4018/markdown-heading-non-headings | 17 |
2 files changed, 23 insertions, 0 deletions
diff --git a/t/t4018/markdown-heading-indented b/t/t4018/markdown-heading-indented new file mode 100644 index 0000000000..1991c2bd45 --- /dev/null +++ b/t/t4018/markdown-heading-indented @@ -0,0 +1,6 @@ +Indented headings are allowed, as long as the indent is no more than 3 spaces. + + ### RIGHT + +- something +- ChangeMe diff --git a/t/t4018/markdown-heading-non-headings b/t/t4018/markdown-heading-non-headings new file mode 100644 index 0000000000..c479c1a3f1 --- /dev/null +++ b/t/t4018/markdown-heading-non-headings @@ -0,0 +1,17 @@ +Headings can be right next to other lines of the file: +# RIGHT +Indents of four or more spaces make a code block: + + # code comment, not heading + +If there's no space after the final hash, it's not a heading: + +#hashtag + +Sequences of more than 6 hashes don't make a heading: + +####### over-enthusiastic heading + +So the detected heading should be right up at the start of this file. + +ChangeMe |