How to use GitHub admonitions ( also known as GitHub Alerts or Callouts )
Learn how to use GitHub's callout boxes like [!NOTE], [!WARNING], and [!TIP] to improve clarity in issues, PRs, and wikis. Copy-paste friendly guide included.
Published on August 3, 2025 by Michael Andreuzza
GitHub now supports a cleaner way to highlight important notes, warnings, and tips in your issues, discussions, pull requests, and wikis — using admonition-style callouts like [!NOTE], [!TIP], and [!WARNING].
These styled boxes make your Markdown more readable, especially when you’re writing long bug reports or sharing best practices.
What are GitHub admonitions?
GitHub Admonitions are special blockquotes with a label inside square brackets — like [!NOTE]. They render as styled callout boxes.
This pattern is now supported in:
Issues
Discussions
PR descriptions
Wikis
README.md or other repo Markdown files (not yet!)
GitHub admonitions cheat sheet
[!NOTE]
> [!NOTE]> This is a regular note with neutral info.
[!NOTE]
This is a regular note with neutral info.
[!TIP]
> [!TIP]> Here's a helpful trick or shortcut!
[!TIP]
Here’s a helpful trick or shortcut!
[!IMPORTANT]
> [!IMPORTANT]> You must configure this before deploying.
[!IMPORTANT]
You must configure this before deploying.
[!WARNING]
> [!WARNING]> Proceed with caution. This can cause issues.
[!WARNING]
Proceed with caution. This can cause issues.
[!CAUTION]
> [!CAUTION]> This action is potentially dangerous.
[!CAUTION]
This action is potentially dangerous.
Not supported in README.md
At the time of writing, these callouts do not render inside README.md files or Markdown content in the repo tree. If you need to simulate them, use emoji blockquotes:
> **Warning:** This is a warning message.
Warning: This is a warning message.
Tips for better usage
Add an empty line before the block to make sure GitHub renders it correctly.
You can use multiple admonitions in one post to break up long content.
Keep your messages short and scannable — use bold text for keywords.
GitHub’s callouts are a small feature with big impact. Use them to keep your communication clear, actionable, and professional, especially when working in a team or contributing to open source.
/Michael Andreuzza
Did you like this post? Please share it with your friends!