Skip to content

Conversation

@lovesegfault
Copy link
Member

@lovesegfault lovesegfault commented Nov 26, 2025

Motivation

Just early days, partially a side-port of how Lix achieved this :)

Context

Fixes: #11839


Add 👍 to pull requests you find important.

The Nix maintainer team uses a GitHub project board to schedule and track reviews.

@xokdvium
Copy link
Contributor

Needs proper attribution to lix contributors tho

@lovesegfault
Copy link
Member Author

Yeah, I think we need to figure out how to do that (Co-Authored-By vs. notice in files vs. referencing the change-id from gerrit in the commit, etc)

- Add meson infrastructure for clang-tidy in nix-meson-build-support/common/clang-tidy/
  with compile_commands.json cleaning and parallel runner
- Create custom clang-tidy plugin scaffolding in src/clang-tidy-plugin/
- Add enableClangTidyLayer in packaging/components.nix that runs clang-tidy
  on all C++ components via postBuild hook
- Add clangTidy Hydra job in packaging/hydra.nix
- Add clang-tidy CI job in .github/workflows/ci.yml to enforce on PRs
- Document usage in doc/manual/source/development/static-analysis.md

Uses debug build mode and skips tests for faster CI. Warnings are treated
as errors to catch issues early.
@Mic92
Copy link
Member

Mic92 commented Nov 27, 2025

Yeah, I think we need to figure out how to do that (Co-Authored-By vs. notice in files vs. referencing the change-id from gerrit in the commit, etc)

Co-authored-by is what we tended to do and referencing commit urls in messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Making use of static analysis to find bugs and UB

3 participants