From c6fa5b6ba0a01a8a0ec53f55e9da06cae5011ecb Mon Sep 17 00:00:00 2001 From: Eduardo Almeida Date: Fri, 18 Oct 2024 13:58:24 +0100 Subject: [PATCH] Fix Markdown lint warnings (MD033) MD033 - Inline HTML --- CONTRIBUTING.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e6d421513..4e5299f6c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -150,8 +150,9 @@ The process described here has several goals: Please follow these steps to have your contribution considered by the maintainers: -1. Follow the [styleguides](#styleguides) -2. After you submit your merge request, verify that all status checks are passing
What if the status checks are failing?If a status check is failing, and you believe that the failure is unrelated to your change, please leave a comment on the merge request explaining why you believe the failure is unrelated. A maintainer will re-run the status check for you. If we conclude that the failure was a false positive, then we will open an issue to track that problem with our status check suite.
+* Follow the [styleguides](#styleguides) +* After you submit your merge request, verify that all status checks are passing. + * If a status check is failing, and you believe that the failure is unrelated to your change, please leave a comment on the merge request explaining why you believe the failure is unrelated. A maintainer will re-run the status check for you. If we conclude that the failure was a false positive, then we will open an issue to track that problem with our status check suite. While the prerequisites above must be satisfied prior to having your merge request reviewed, the reviewer(s) may ask you to complete additional design work, tests, or other changes before your merge request can be ultimately accepted.