Github markdown: Difference between revisions
From wikinotes
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
|} | |} | ||
</blockquote><!-- Documentation --> | </blockquote><!-- Documentation --> | ||
= PRs/Issues = | |||
<blockquote> | |||
The keyword <code>fixes, closes, resolves</code> followed by an ISSUE will automatically close the issue when the PR is merged. | |||
See https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue | |||
</blockquote><!-- PRs/Issues --> | |||
Latest revision as of 15:53, 19 September 2021
Github's markdown parser adheres to the commonmark spec, and introduces some extensions of it's own.
I believe it uses c hoedown as a parser, but I'm not certain.
Documentation
official docs https://github.github.com/gfm/
PRs/Issues
The keyword
fixes, closes, resolvesfollowed by an ISSUE will automatically close the issue when the PR is merged.See https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue
