Right-to-left languages are now supported natively in Markdown files, issues, pull requests, discussions, and comments.
Do you think they could be even better? Let us know how we can improve by contributing to our discussion.
You can now quickly create a Markdown link in all Markdown-enabled fields, like issue comments and pull request descriptions, by pasting a URL on text that you have previously selected.
Learn more about writing and formatting on GitHub.
We've added keyboard shortcuts for quotes and lists in Markdown files, issues, PRs and comments.
To add quotes, use cmd+shift+. on Mac or ctrl+shift+. on Windows/Linux.
To add an ordered list, use cmd+shift+7 on Mac or ctrl+shift+7 on Windows/Linux.
To add an unordered list, use cmd+shift+8 on Mac or ctrl+shift+8 on Windows/Linux.
For a full list of all our keyboard shortcuts, see our docs.
You can now choose to use a fixed-width font in Markdown-enabled fields, like issue comments and pull request descriptions. Currently these fields use a variable-width font, which can make it difficult to edit advanced Markdown structures like tables and code snippets.
To enable, go to your appearance settings and toggle on Use a fixed-width (monospace) font when editing Markdown in the “Markdown editor font preference” section.
Learn more about writing and formatting on GitHub.
Footnotes let you reference relevant information without disrupting the flow of what you're trying to say:
Here is a simple footnote[^1]. With some additional text after it.
[^1]: My reference.You can now use footnote syntax in any Markdown field!
Footnotes are displayed as superscript links. Click them to jump to their referenced information, displayed in a new section at the bottom of the document:
Learn more about using footnotes in Markdown.
You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information on supported file types, see the documentation.
Today we are announcing new beta features within GitHub Issues, with better ways to plan, track, and manage projects.
Read more on the GitHub Issues page or in the FAQ.
✨ NEW – Project planning for developers
Available in limited public beta
Built like a spreadsheet, project tables give you a live canvas to filter, sort, and group issues and pull requests. Tailor them to your needs with custom fields and saved views. Sign up for the beta now.
- Prioritize your work across repositories with a new spreadsheet-like table
- Extend issues with custom fields with support for text, number, date and single-select types
- Change custom field values right from the issues sidebar
- Filter, sort, and group by any field
- Instantly switch between project tables and boards
- Save your view options to share with your team
- Build custom workflows with a GraphQL API to access project issues and metadata
- Use cmd + k to bring up a command palette that lets you filter, sort, group, and manage views
✨ NEW – Break issues into actionable tasks
Available in public beta
When lists of tasks are created in markdown and referenced in another issue, this will now create a dynamic relationship that helps you break down your work and track it to completion. Convert text into issues quickly after brainstorming ideas with your team, and stay up to date on progress now that tracked issues are automatically checked off when closed.
- Create task lists of issues and pull requests
- Quickly convert text into issues
- Track status of tasks with progress indicators
- See which issues another issue is being tracked in
- Automatically update the status of a task when the tracked issue is closed
📣 Got feedback?
Join our feedback community and let us know how we can improve.
Video upload is now supported everywhere you can author Markdown in GitHub, including from the mobile app. Share demos, show reproduction steps, and more in issue, pull request, and discussion comments as well as on repository Markdown files such as READMEs.
Learn more about uploading videos and check out the blog post for more details.
