To create a heading, add one to six # symbols before your heading text. The number of # you use will determine the size of the heading.
# The largest heading ## The second largest heading ###### The smallest heading
When you use two or more headings, GitHub automatically generates a table of contents which you can access by clicking within the file header. Each heading title is listed in the table of contents and you can click a title to navigate to the selected section.
You can indicate emphasis with bold, italic, or strikethrough text in comment fields and
|Bold||Command+B (Mac) or Ctrl+B (Windows/Linux)||This is bold text|
|Italic||Command+I (Mac) or Ctrl+I (Windows/Linux)||This text is italicized|
|Bold and nested italic||This text is extremely important|
|All bold and italic||All this text is important|
You can quote text with a >.
Text that is not a quote > Text that is a quote
Tip: When viewing a conversation, you can automatically quote text in a comment by highlighting the text, then typing R. You can quote an entire comment by clicking , then Quote reply. For more information about keyboard shortcuts, see "Keyboard shortcuts."
You can call out code or a command within a sentence with single backticks. The text within the backticks will not be formatted. You can also press the Command+E (Mac) or Ctrl+E (Windows/Linux) keyboard shortcut to insert the backticks for a code block within a line of Markdown.
Use `git status` to list all new or modified files that haven't yet been committed.
To format code or text into its own distinct block, use triple backticks.
Some basic Git commands are: ``` git status git add git commit ```
For more information, see "Creating and highlighting code blocks."
You can create an inline link by wrapping link text in brackets
[ ], and then wrapping the URL in parentheses
( ). You can also use the keyboard shortcut Command+K to create a link.
This site was built using [GitHub Pages](https://pages.github.com/).
Tip: GitHub Enterprise Server automatically creates links when valid URLs are written in a comment. For more information, see "Autolinked references and URLs."
You can link directly to a section in a rendered file by hovering over the section heading to expose the link:
You can define relative links and image paths in your rendered files to help readers navigate to other files in your repository.
A relative link is a link that is relative to the current file. For example, if you have a README file in root of your repository, and you have another file in docs/CONTRIBUTING.md, the relative link to CONTRIBUTING.md in your README might look like this:
[Contribution guidelines for this project](docs/CONTRIBUTING.md)
GitHub Enterprise Server will automatically transform your relative link or image path based on whatever branch you're currently on, so that the link or path always works. You can use all relative link operands, such as
Relative links are easier for users who clone your repository. Absolute links may not work in clones of your repository - we recommend using relative links to refer to other files within your repository.
You can display an image by adding ! and wrapping the alt text in
[ ]. Then wrap the link for the image in parentheses
![This is an image](https://myoctocat.com/assets/images/base-octocat.svg)
GitHub Enterprise Server supports embedding images into your issues, pull requests, comments and
.md files. You can display an image from your repository, add a link to an online image, or upload an image. For more information, see "Uploading assets."
Tip: When you want to display an image which is in your repository, you should use relative links instead of absolute links.
Here are some examples for using relative links to display an image.
|In a |
|In a |
|In issues, pull requests and comments of the repository|
|In a |
|In issues, pull requests and comments of another repository|
Note: The last two relative links in the table above will work for images in a private repository only if the viewer has at least read access to the private repository which contains these images.
For more information, see "Relative Links."
You can make an unordered list by preceding one or more lines of text with - or *.
- George Washington - John Adams - Thomas Jefferson
To order your list, precede each line with a number.
1. James Madison 2. James Monroe 3. John Quincy Adams
You can create a nested list by indenting one or more list items below another item.
To create a nested list using the web editor on GitHub Enterprise Server or a text editor that uses a monospaced font, like Atom, you can align your list visually. Type space characters in front of your nested list item, until the list marker character (- or *) lies directly below the first character of the text in the item above it.
1. First list item - First nested list item - Second nested list item
Note: In the web-based editor, you can indent or dedent one or more lines of text by first highlighting the desired lines and then using Tab or Shift+Tab respectively.
To create a nested list in the comment editor on GitHub Enterprise Server, which doesn't use a monospaced font, you can look at the list item immediately above the nested list and count the number of characters that appear before the content of the item. Then type that number of space characters in front of the nested list item.
In this example, you could add a nested list item under the list item
100. First list item by indenting the nested list item a minimum of five spaces, since there are five characters (
100. ) before
First list item.
100. First list item - First nested list item
You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven characters (
␣␣␣␣␣-␣) before the nested list content
First nested list item, you would need to indent the second nested list item by seven spaces.
100. First list item - First nested list item - Second nested list item
For more examples, see the GitHub Flavored Markdown Spec.
To create a task list, preface list items with a hyphen and space followed by
[ ]. To mark a task as complete, use
- [x] #739 - [ ] https://github.com/octo-org/octo-repo/issues/740 - [ ] Add delight to the experience when all tasks are complete :tada:
If a task list item description begins with a parenthesis, you'll need to escape it with \:
- [ ] \(Optional) Open a followup issue
For more information, see "About task lists."
You can mention a person or team on GitHub Enterprise Server by typing @ plus their username or team name. This will trigger a notification and bring their attention to the conversation. People will also receive a notification if you edit a comment to mention their username or team name. For more information about notifications, see "About notifications."
Note: A person will only be notified about a mention if the person has read access to the repository and, if the repository is owned by an organization, the person is a member of the organization.
@github/support What do you think about these updates?
When you mention a parent team, members of its child teams also receive notifications, simplifying communication with multiple groups of people. For more information, see "About teams."
Typing an @ symbol will bring up a list of people or teams on a project. The list filters as you type, so once you find the name of the person or team you are looking for, you can use the arrow keys to select it and press either tab or enter to complete the name. For teams, enter the @organization/team-name and all members of that team will get subscribed to the conversation.
The autocomplete results are restricted to repository collaborators and any other participants on the thread.
You can bring up a list of suggested issues and pull requests within the repository by typing #. Type the issue or pull request number or title to filter the list, and then press either tab or enter to complete the highlighted result.
For more information, see "Autolinked references and URLs."
If custom autolink references are configured for a repository, then references to external resources, like a JIRA issue or Zendesk ticket, convert into shortened links. To know which autolinks are available in your repository, contact someone with admin permissions to the repository. For more information, see "Configuring autolinks to reference external resources."
Some GitHub Apps provide information in GitHub Enterprise Server for URLs that link to their registered domains. GitHub Enterprise Server renders the information provided by the app under the URL in the body or comment of an issue or pull request.
To see content attachments, you must have a GitHub App that uses the Content Attachments API installed on the repository.
Content attachments will not be displayed for URLs that are part of a markdown link.
For more information about building a GitHub App that uses content attachments, see "Using Content Attachments."
You can upload assets like images by dragging and dropping, selecting from a file browser, or pasting. You can upload assets to issues, pull requests, comments, and
.md files in your repository.
You can add emoji to your writing by typing
@octocat :+1: This PR looks great - it's ready to merge! :shipit:
Typing : will bring up a list of suggested emoji. The list will filter as you type, so once you find the emoji you're looking for, press Tab or Enter to complete the highlighted result.
For a full list of available emoji and codes, check out the Emoji-Cheat-Sheet.
You can create a new paragraph by leaving a blank line between lines of text.
You can tell GitHub Enterprise Server to hide content from the rendered Markdown by placing the content in an HTML comment.
<!-- This content will not appear in the rendered Markdown -->
You can tell GitHub Enterprise Server to ignore (or escape) Markdown formatting by using \ before the Markdown character.
Let's rename \*our-new-project\* to \*our-old-project\*.
For more information, see Daring Fireball's "Markdown Syntax."