GitHub uses its own Markdown processor, which is a variant of the CommonMark specification. This means that while it supports most of the standard Markdown syntax, there are some GitHub-specific extensions and features. You can use Markdown syntax, along with some additional HTML tags, to format your writing on GitHub, in places like repository READMEs and comments on pull requests and issues.
For more examples, see the GitHub Flavored Markdown Spec.
See Writing on GitHub for more details.
To create a heading, add one to six # symbols before your heading text. The number of # you use will determine the hierarchy level and typeface size of the heading.
This text is bold This text is bold and this is a link
This text is italic
This text is strikethrough
This text is bold with nested italic
This text is bold and italic
This text is subscript
This text is superscript
This text is underlined
This is a keyboard shortcut
This is a blockquote.
This is a inline code example.
print("This is a Python3 code block")
In issues, pull requests, and discussions, you can call out colors within a sentence by using backticks. A supported color model within backticks will display a visualization of the color.
The background color is #ffffff for light mode and #000000 for dark mode, also rgb(9, 105, 218).
This site was built using GitHub Pages.
You can link to a section of a page by using the section's heading text, with spaces replaced by hyphens and all lowercase.
Link to the previous section: Links.
Link to a file in the same repository: README.md.
Some body text of this section.
Some text I want to provide a direct link to, but which doesn't have its own heading.
(… more content…)
To create a line break, end a line with two or more spaces, and then type return.
Line one.
Line two.
or use the HTML <br> tag.
Line one.
Line two.

You can make an unordered list by preceding one or more lines of text with -, *, or +.
To order your list, precede each line with a number.
You can tell GitHub to ignore (or escape) Markdown formatting by using \ before the Markdown character.
Let's rename *our-new-project* to *our-old-project*.

Hi, I'm Mona. You might recognize me as GitHub's mascot.
| Rank | Languages |
|---|---|
| 1 | JavaScript |
| 2 | Python |
| 3 | SQL |
| Rank | Languages |
|---|---|
| 1 | JavaScript |
| 2 | Python |
| 3 | SQL |
We can't use an <iframe> tag to embed a video, but we can link to a video on YouTube or another site and display a thumbnail image that links to the video.
If we pull together and commit ourselves, then we can push through anything.
— Mona the Octocat
| Left-aligned | Center-aligned | Right-aligned |
|---|---|---|
| git status | git status | git status |
| git diff | git diff | git diff |
| Pipe | | |
| Command | Description |
|---|---|
git status | List all new or modified files |
git diff | Show file differences that haven't been staged |
You can add text within a collapsed section.
You can add an image or a code block, too.
puts "Hello World"
The <iframe> tag is not supported in GitHub Markdown. You can link to an external site instead.