Skip to content

Commit 37fe8b5

Browse files
committed
Use New Markdown Alerts
1 parent bbedf53 commit 37fe8b5

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

.github/contributing.md

+4-2
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,8 @@ This project and everyone participating in it is governed by the [Marlin Code of
3030

3131
## I don't want to read this whole thing I just have a question!!!
3232

33-
> **Note:** Please don't file an issue to ask a question. You'll get faster results by using the resources below.
33+
> [!NOTE]
34+
> Please don't file an issue to ask a question. You'll get faster results by using the resources below.
3435
3536
We have a Message Board and a Facebook group where our knowledgable user community can provide helpful advice if you have questions.
3637

@@ -55,7 +56,8 @@ This section guides you through submitting a Bug Report for Marlin. Following th
5556

5657
Before creating a Bug Report, please test the "nightly" development branch, as you might find out that you don't need to create one. When you are creating a Bug Report, please [include as many details as possible](#how-do-i-submit-a-good-bug-report). Fill out [the required template](ISSUE_TEMPLATE/bug_report.yml), the information it asks for helps us resolve issues faster.
5758

58-
> **Note:** Regressions can happen. If you find a **Closed** issue that seems like your issue, go ahead and open a new issue and include a link to the original issue in the body of your new one. All you need to create a link is the issue number, preceded by #. For example, #8888.
59+
> [!NOTE]
60+
> Regressions can happen. If you find a **Closed** issue that seems like your issue, go ahead and open a new issue and include a link to the original issue in the body of your new one. All you need to create a link is the issue number, preceded by #. For example, #8888.
5961
6062
#### How Do I Submit A (Good) Bug Report?
6163

0 commit comments

Comments
 (0)