[llvm-branch-commits] [clang-tools-extra] release/20.x: [clang-tidy] Do not pass any file when listing checks in run_clang_ti… (#137286) (PR #137775)

2025-05-03 Thread Carlos Galvez via llvm-branch-commits
carlosgalvezp wrote: @HerrCai0907 Could you approve the PR so we can bring it to the release? https://github.com/llvm/llvm-project/pull/137775 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailma

[llvm-branch-commits] [clang-tools-extra] release/20.x: [clang-tidy] Do not pass any file when listing checks in run_clang_ti… (#137286) (PR #137775)

2025-04-30 Thread Carlos Galvez via llvm-branch-commits
https://github.com/carlosgalvezp updated https://github.com/llvm/llvm-project/pull/137775 >From 387c2886b68b1eaf68916e4b08e8d92966a1 Mon Sep 17 00:00:00 2001 From: Carlos Galvez Date: Tue, 29 Apr 2025 11:13:30 +0200 Subject: [PATCH] =?UTF-8?q?[clang-tidy]=20Do=20not=20pass=20any=20file=20w?

[llvm-branch-commits] [clang-tools-extra] release/20.x: [clang-tidy] Fix broken HeaderFilterRegex when read from config file (#133582) (PR #134215)

2025-04-08 Thread Carlos Galvez via llvm-branch-commits
carlosgalvezp wrote: @tstellar Can you advice on what the next steps are to get this merged into the release branch? https://github.com/llvm/llvm-project/pull/134215 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists

[llvm-branch-commits] [clang-tools-extra] release/20.x: [clang-tidy] Fix broken HeaderFilterRegex when read from config file (#133582) (PR #134215)

2025-04-04 Thread Carlos Galvez via llvm-branch-commits
https://github.com/carlosgalvezp updated https://github.com/llvm/llvm-project/pull/134215 >From d868cc50a9aa0884a360c20179a8a921417d867c Mon Sep 17 00:00:00 2001 From: Carlos Galvez Date: Thu, 3 Apr 2025 09:28:34 +0200 Subject: [PATCH] [clang-tidy] Fix broken HeaderFilterRegex when read from c

[llvm-branch-commits] [clang-tools-extra] release/20.x: [clang-tidy] Fix broken HeaderFilterRegex when read from config file (#133582) (PR #134215)

2025-04-04 Thread Carlos Galvez via llvm-branch-commits
carlosgalvezp wrote: > It's ok as far as it works. Personally if we do not utilize that optional, > then probably it should be removed. It's essentially a revert. I agree that our usage of optional in the Options is not good, we should improve that on a separate patch. https://github.com/llvm