• TL;DR Add non-blocking precommit clang-tidy analysis to LLVM’s CI on per-component basis. • Component maintainers (like mlir , clang , lldb , ..) will decide if precommit clang-tidy analysis is needed. • This RFC don’t propose to enforce clang-tidy on whole LLVM at once. • If you feel that enabling clang-tidy for your component will be a overall a net-loss, feel free not to do so. • Rationale clang-tidy is a C++ linter tool developed under LLVM umbrella. • Having it in precommit CI will give us the following benefits: - Less load on maintainers during review: clang-tidy can automatically check naming style, LLVM code conventions.

Article Summaries:

  • Summary

The LLVM project has proposed a new RFC to add non‑blocking pre‑commit clang‑tidy checks to its continuous‑integration pipeline on a per‑component basis. Instead of enforcing clang‑tidy across the entire codebase, component maintainers (e.g., mlir, clang, lldb) will decide whether to enable the checks for their modules. The goal is to reduce reviewer workload, catch subtle bugs early, and gradually modernize the codebase. The plan includes selecting initial components, configuring relevant checks, clearing legacy warnings, and setting up CI infrastructure that runs clang‑tidy only on specified directories. The proposal invites maintainers to adopt the framework and provide feedback.

Sources: