Skip to content

Disable more clang-tidy checks#564

Open
gaul wants to merge 2 commits intointel:thermald_nextfrom
gaul:error-prone/disable
Open

Disable more clang-tidy checks#564
gaul wants to merge 2 commits intointel:thermald_nextfrom
gaul:error-prone/disable

Conversation

@gaul
Copy link
Copy Markdown
Contributor

@gaul gaul commented May 6, 2026

This is sufficient to compile warning-free with clang-tidy 22.

This is sufficient to compile warning-free with clang-tidy 22.

Signed-off-by: Andrew Gaul <andrew@gaul.org>
@gaul gaul force-pushed the error-prone/disable branch from 638b173 to d41b487 Compare May 6, 2026 00:13
@gaul gaul changed the title Disable more error-prone checks Disable more clang-tidy checks May 6, 2026
@spandruvada spandruvada requested a review from Copilot May 7, 2026 17:31
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the project’s clang-tidy configuration and invocation to achieve a warning-free run with clang-tidy 22.

Changes:

  • Updates the clang-tidy Makefile target to pass an explicit C++ standard and adjust header filtering behavior.
  • Disables additional bugprone-* checks in .clang-tidy to avoid new warnings introduced by clang-tidy 22.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
Makefile.am Adjusts the clang-tidy target arguments (C++ standard / header filtering) to match clang-tidy 22 behavior.
.clang-tidy Expands the disabled-check list to reduce clang-tidy 22 warnings.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread Makefile.am Outdated
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants