Where is GitHub Flavored Markdown (GFM) actually used in GitHub?

This has been a mystery to me for a while, and for some reason Google didn’t help me, so let me ask.

EDIT: ok, I understand the GFM is everywhere in GitHub, and why GFM style line break edit is not available?? Is it turned off? and I know the original MD rule. What I’d like to confirm here is GFM line break rule. Thank you.

  • git merge: PR on master “messed” up my test branch, how do I fix it?
  • Update github markdown Tasklists ( GFM ) via commit
  • GIT Thinks I've made changes when I haven't
  • Unable to resolve reference refs /refs/remotes/origin/branch while pushing after merging branches
  • Which will get Priority between “github pages” and “directory kept at root” in case of name conflicts and why
  • what's better? deleting file and using git add -u or git rm
  • I like GFM very much especially for the straightfoward line break manner.
    However, I have been never able to post my own Markdown with this line beak mode.

    For instance, I copied some syntax list MD to a new page of one of my wiki on GitHub.


    As you can confirm the MD source.

    This is intended as a quick reference and showcase. 
    For more complete info, see [John Gruber's original spec]

    a single new line is applied; however, the result shown with no new line.

    What do I miss? Where is GitHub Flavored Markdown (GFM) is actually used in GitHub?

    (Technical note: Markdown Here uses GFM line breaks, so there’s no need to use MD’s two-space line breaks.)

    It certainly says so, but I found this md uses 2 spaces br manner.

  • Teamcity trigger builds for github pull-requests
  • Pull request merged, closed, then reverted - now can't pull the branch again
  • Cross-Origin Resource Sharing on GitHub Pages
  • Check multiple subdirectories using AppVeyor
  • How do I prevent the GitHub Pages “Automatic Generator” to remove everything before regenerate the site?
  • git push error: the requested URL returned error 400
  • 3 Solutions collect form web for “Where is GitHub Flavored Markdown (GFM) actually used in GitHub?”

    Contrary to the other answers, GFM is only used where text is only entered through the GitHub website, not in README.md and not on GitHub Wikis.

    From https://help.github.com/articles/github-flavored-markdown (emphasis added)

    GitHub uses what we’re calling “GitHub Flavored Markdown” (GFM) for
    messages, issues, and comments.

    The reasoning behind this is that README.md and Wikis are part of Git repositories, and therefore can be cloned outside of the site, where one would reasonably expect (standard) Markdown rather than GFM.

    For more on GitHub’s rationale, see https://github.com/github/markup/issues/208#issuecomment-24927799


    Syntax highlighting (Pygments) is separate from GFM, in that, GFM employs syntax highlighting, however the presence of syntax highlighting does not entail GFM, hence why GitHub Pages will use standard Markdown line-breaks: it uses Pygments, but not GFM.

    It’s used when you display your README.md file on your repository front page, for example. Also, when you add comments it’s GFM.

    github flavored markdown is used on:

    • your repo’s readme file
    • any .md files in your repo
    • issues
    • wikis & pages

    and minimally on comments (commit, pull requests, etc)

    a note about issues: it seems like it uses a limited version of GFM than on wiki pages or readme files.

    Git Baby is a git and github fan, let's start git clone.