# ⚠️ GitHub is beta testing their own Admonition syntax. We should weigh in

**URL:** <https://talk.commonmark.org/t/github-is-beta-testing-their-own-admonition-syntax-we-should-weigh-in/4173>\
**Category:** Extensions\
**Created:** [May 26, 2022, 10:08pm UTC](https://talk.commonmark.org/t/github-is-beta-testing-their-own-admonition-syntax-we-should-weigh-in/4173 "2022-05-26T22:08:54Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Brian\_Lalonde](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/brian_lalonde/32/1565_2.png) [@Brian\_Lalonde](https://talk.commonmark.org/u/Brian_Lalonde)\
**Post date:** [June 2, 2022, 3:25pm UTC](https://talk.commonmark.org/t/github-is-beta-testing-their-own-admonition-syntax-we-should-weigh-in/4173/6 "2022-06-02T15:25:55Z")

</div>

The PowerShell documentation team at Microsoft uses [a similar extension](https://docs.microsoft.com/powershell/scripting/community/contributing/powershell-style-guide) for admonitions, closer to @Crissov 's suggestion:

```markdown
> [!NOTE]
> Information the user should notice even if skimming.

> [!TIP]
> Optional information to help a user be more successful.

> [!IMPORTANT]
> Essential information required for user success.

> [!CAUTION]
> Negative potential consequences of an action.

> [!WARNING]
> Dangerous certain consequences of an action.

```

 ![image](https://cdn.commonmark.org/uploads/default/original/2X/7/7b36dca7c2290cd0f4aa7214c56c6c876e5f277f.png)

---

_[View the full topic](https://talk.commonmark.org/t/github-is-beta-testing-their-own-admonition-syntax-we-should-weigh-in/4173)._