Which callout types map to a GitHub alert?

note, tip, important, warning, and caution map directly. Common Obsidian aliases are mapped to the nearest GitHub type — info and todo to NOTE, hint and success to TIP, question and help to IMPORTANT, attention to WARNING, and danger, error, bug, or failure to CAUTION.

Why is the callout title on its own line?

GitHub ignores an alert whose first line carries extra text. The title is moved to the next line in bold so the wording survives and the alert still renders.

What happens to an unknown callout type?

It becomes a plain blockquote with the title, or the type name, in bold. That renders correctly in every Markdown renderer instead of showing raw [!type] text.

Obsidian to Markdown guide

Convert Obsidian Callouts to GitHub Markdown Alerts

Obsidian callouts use > [!note] Title. GitHub supports five alert types with uppercase names and no inline title. Here is the mapping the converter applies.

Direct answer

GitHub renders exactly five alert types: NOTE, TIP, IMPORTANT, WARNING, and CAUTION, written as a blockquote line > [!NOTE] with no title on the same line. The converter uppercases matching Obsidian callout types, moves any inline title onto the next line in bold, and drops the +/- fold markers. A callout type GitHub does not support, such as [!cite] or [!example], becomes a plain blockquote with a bold label so it still renders everywhere.

Open the Obsidian ↔ Markdown converter

When to use this

You are publishing vault notes as a README or a GitHub wiki page.
Callouts appear as literal [!warning] text after export.
You want warnings to keep their visual weight outside Obsidian.

Steps

Paste the note into the converter above with the direction on Obsidian → standard Markdown.
Find the callouts in the output and confirm the type mapped the way you want.
Check any callout that was not one of the five GitHub types; it is now a bold-labelled blockquote.
Copy the result into the README, issue, or wiki page.
Preview on GitHub, because alert rendering only appears in GitHub's own renderer.

Example conversion

Input

> [!warning] Check the backup first
> The restore path is not tested.

> [!cite] Internal RFC 12

Converted output

> [!WARNING]
> **Check the backup first**
> The restore path is not tested.

> **Internal RFC 12**

Common mistakes

Do not keep the fold markers. > [!note]- means collapsed in Obsidian and nothing anywhere else, so the converter removes it.
Do not expect nested callouts to survive as callouts. Nested blockquote lines stay blockquote lines, and only the header line of each callout is rewritten.
Do not assume every renderer draws the alert box. GitHub does; most other Markdown renderers show a normal blockquote with the [!NOTE] line visible.

FAQ

Which callout types map to a GitHub alert?: note, tip, important, warning, and caution map directly. Common Obsidian aliases are mapped to the nearest GitHub type — info and todo to NOTE, hint and success to TIP, question and help to IMPORTANT, attention to WARNING, and danger, error, bug, or failure to CAUTION.
Why is the callout title on its own line?: GitHub ignores an alert whose first line carries extra text. The title is moved to the next line in bold so the wording survives and the alert still renders.
What happens to an unknown callout type?: It becomes a plain blockquote with the title, or the type name, in bold. That renders correctly in every Markdown renderer instead of showing raw [!type] text.

Convert Obsidian Callouts to GitHub Markdown Alerts

Direct answer

When to use this

Steps

Example conversion

Common mistakes

FAQ

Related Obsidian guides

How to Convert Obsidian Wikilinks to Standard Markdown

Export Obsidian Notes to GitHub Without Broken Links

Obsidian Frontmatter and Tags: What to Keep When You Export

Turn an Obsidian Vault Note Into Portable Markdown