[clang-tools-extra] [clang-tidy][docs] Note MISRA/AUTOSAR checks are not accepted (PR #214661)

[via cfe-commits]

https://github.com/richardmilles updated https://github.com/llvm/llvm-project/pull/214661

>From e1effd306fe102b760cacff7582d91b9338b908b Mon Sep 17 00:00:00 2001
From: richardmilles <darkenhalneke at gmail.com>
Date: Fri, 7 Aug 2026 10:24:26 +0200
Subject: [PATCH] [clang-tidy][docs] Note MISRA/AUTOSAR checks are not accepted

Fixes #160940

Co-authored-by: Cursor <cursoragent at cursor.com>
---
 clang-tools-extra/docs/clang-tidy/Contributing.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/clang-tools-extra/docs/clang-tidy/Contributing.rst b/clang-tools-extra/docs/clang-tidy/Contributing.rst
index 438d57562f00b..1aafd7dc7faff 100644
--- a/clang-tools-extra/docs/clang-tidy/Contributing.rst
+++ b/clang-tools-extra/docs/clang-tidy/Contributing.rst
@@ -455,6 +455,12 @@ If your check relates to a published coding guideline (C++ Core Guidelines,
 SEI CERT, etc.) or style guide, provide links to the relevant guideline or
 style guide sections in your check documentation.
 
+Checks that directly reference MISRA or AUTOSAR guidelines are not accepted
+due to legal/license reasons; see
+`this Discourse thread <https://discourse.llvm.org/t/will-clang-frontend-plan-accept-misra-check-tools/84754>`_.
+Generic checks that happen to overlap with those guidelines are fine as long as
+they do not claim to implement or link to MISRA/AUTOSAR rules.
+
 Provide enough examples of the diagnostics and fix-its provided by the check so
 that a user can easily understand what will happen to their code when the check
 is run. If there are exceptions or limitations to your check, document them