llvmorg-github-actions[bot] wrote:
<!--LLVM PR SUMMARY COMMENT--> @llvm/pr-subscribers-clang-tidy Author: richardmilles <details> <summary>Changes</summary> Document that checks directly referencing MISRA/AUTOSAR are not accepted (legal/license). Generic overlapping checks without such links remain fine. Fixes #<!-- -->160940 Assisted-by: Cursor Made with [Cursor](https://cursor.com) --- Full diff: https://github.com/llvm/llvm-project/pull/214661.diff 1 Files Affected: - (modified) clang-tools-extra/docs/clang-tidy/Contributing.rst (+6) ``````````diff 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 `````````` </details> https://github.com/llvm/llvm-project/pull/214661 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
