GitHub uses "GitHub Flavored Markdown," or GFM, across the site--in issues, comments, and pull requests. It differs from standard Markdown (SM) in a few significant ways, and adds some additional functionality.
[2] GitHub Help
()
https://help.github.com/categories/writing-on-github/
[3] Basic writing and formatting syntax - User Documentation () https://help.github.com/articles/basic-writing-and-formatting-syntax/
[6] A formal spec for GitHub Flavored Markdown | GitHub Engineering
(Vicent Martí著, )
https://githubengineering.com/a-formal-spec-for-github-markdown/
[8] github/cmark: GitHub's fork of cmark, a CommonMark parsing and rendering library and program in C
()
https://github.com/github/cmark/
cmark-gfm is an extended version of the C reference implementation of CommonMark, a rationalized version of Markdown syntax with a spec. This repository adds GitHub Flavored Markdown extensions to the upstream implementation, as defined in the spec.
[12] Mooseさんのツイート: ". @github changed their Markdown parser and broke a lot of our documentation. Backwards compatibility, it matters."
()
https://twitter.com/mustpax/status/865406109523206144
[13] Artem Zinnatullinさんのツイート: "Shame @github wasn't able to keep compatibility w/ #Headers in markdown for commits made before their md change. Lots prjcts have to fix it"
()
https://twitter.com/artem_zin/status/846103851933585411
[14] Matt Brobergさんのツイート: "I had a markdown list rendering break and found this ~> A formal spec for GitHub Flavored Markdown https://t.co/cCtcY7Mqqy by @github"
()
https://twitter.com/mbbroberg/status/864222356021145602
[15] Michael Berkowskiさんのツイート: "Did @github markdown change? Seeing lots of README files with unrendered: #Heading1 ##Heading2 ..now requiring whitespace # Heading1"
()
https://twitter.com/mberkowski/status/860528837926543360
[16] Zev Eisenbergさんのツイート: "Did @github recently change the strictness of their Markdown’s header parser? I’ve seen a lot of “####Some Header” recently."
()
https://twitter.com/ZevEisenberg/status/854350219592577025
[17] Alex Sorokoletovさんのツイート: "Hey, @github did you change markdown engine or rules? I literally see lots of repos with ### headers broken. I bet it wasn't like this b4"
()
https://twitter.com/AlexSorokoletov/status/850529454464131072
[18] phnkさんのツイート: "Dear @GitHub – Did you change how GitHub Markdown syntax is parsed? Lists starting with 1. used to be numbered all the way, right? No more? https://t.co/oGXFc6YwSn"
()
https://twitter.com/phnk/status/846008012351377410
[19] A formal spec for GitHub Flavored Markdown | GitHub Engineering
(Vicent Martí著, )
https://githubengineering.com/a-formal-spec-for-github-markdown/
[24] Include diagrams in your Markdown files with Mermaid | The GitHub Blog, https://github.blog/2022-02-14-include-diagrams-markdown-files-mermaid/
[25]
Mermaid, topoJSON, geoJSON, and ASCII STL Diagrams Are Now Supported in Markdown and as Files | GitHub Changelog, https://github.blog/changelog/2022-03-17-mermaid-topojson-geojson-and-ascii-stl-diagrams-are-now-supported-in-markdown-and-as-files/
[26] Render mathematical expressions in Markdown - The GitHub Blog, https://github.blog/changelog/2022-05-19-render-mathematical-expressions-in-markdown/