feat: update README and code to support clang-tidy auto-fix with version v1.4.0

Author: shenxianpeng

README.md

@@ -32,7 +32,7 @@ Add this configuration to your `.pre-commit-config.yaml` file:
 ```yaml
 repos:
   - repo: https://github.com/cpp-linter/cpp-linter-hooks
-    rev: v1.2.0  # Use the tag or commit you want
+    rev: v1.4.0  # Use the tag or commit you want
     hooks:
       - id: clang-format
         args: [--style=Google] # Other coding style: LLVM, GNU, Chromium, Microsoft, Mozilla, WebKit.
@@ -47,7 +47,7 @@ To use custom configurations like `.clang-format` and `.clang-tidy`:
 ```yaml
 repos:
   - repo: https://github.com/cpp-linter/cpp-linter-hooks
-    rev: v1.2.0
+    rev: v1.4.0
     hooks:
       - id: clang-format
         args: [--style=file]  # Loads style from .clang-format file
@@ -56,7 +56,7 @@ repos:
 ```
 
 > [!TIP]
-> The `rev` tag (e.g. `v1.2.0`) is the **project** version, not the clang tool version. Each release bundles a default version of `clang-format` and `clang-tidy` — check the [release notes](https://github.com/cpp-linter/cpp-linter-hooks/releases) to see which tool version a given `rev` ships with. To pin an exact tool version independently of the project release, use `--version` as shown below.
+> The `rev` tag (e.g. `v1.4.0`) is the **project** version, not the clang tool version. Each release bundles a default version of `clang-format` and `clang-tidy` — check the [release notes](https://github.com/cpp-linter/cpp-linter-hooks/releases) to see which tool version a given `rev` ships with. To pin an exact tool version independently of the project release, use `--version` as shown below.
 
 ### Custom Clang Tool Version
 
@@ -65,7 +65,7 @@ To use specific versions of clang-format and clang-tidy (using Python wheel pack
 ```yaml
 repos:
   - repo: https://github.com/cpp-linter/cpp-linter-hooks
-    rev: v1.2.0
+    rev: v1.4.0
     hooks:
       - id: clang-format
         args: [--style=file, --version=21] # Specifies version
@@ -89,7 +89,7 @@ automatically — no configuration needed for most projects:
 ```yaml
 repos:
   - repo: https://github.com/cpp-linter/cpp-linter-hooks
-    rev: v1.2.0
+    rev: v1.4.0
     hooks:
       - id: clang-tidy
         args: [--checks=.clang-tidy]
@@ -204,7 +204,7 @@ Use -header-filter=.* to display errors from all non-system headers. Use -system
 ```yaml
 repos:
   - repo: https://github.com/cpp-linter/cpp-linter-hooks
-    rev: v1.2.0
+    rev: v1.4.0  # requires the version that introduced --fix
     hooks:
       - id: clang-tidy
         args: [--checks=.clang-tidy, --fix]
@@ -223,7 +223,7 @@ repos:
 
 ```yaml
 - repo: https://github.com/cpp-linter/cpp-linter-hooks
-  rev: v1.2.0
+  rev: v1.4.0
   hooks:
     - id: clang-format
       args: [--style=file, --version=21]
@@ -238,7 +238,7 @@ or `-j`:
 
 ```yaml
 - repo: https://github.com/cpp-linter/cpp-linter-hooks
-  rev: v1.2.0
+  rev: v1.4.0
   hooks:
     - id: clang-tidy
       args: [--checks=.clang-tidy, --version=21, --jobs=4]
@@ -267,7 +267,7 @@ This approach ensures that only modified files are checked, further speeding up
 ```yaml
 repos:
   - repo: https://github.com/cpp-linter/cpp-linter-hooks
-    rev: v1.2.0
+    rev: v1.4.0
     hooks:
       - id: clang-format
         args: [--style=file, --version=21, --verbose]   # Shows processed files

cpp_linter_hooks/clang_tidy.py

@@ -155,7 +155,11 @@ def run_clang_tidy(args=None) -> Tuple[int, str]:
 
     clang_tidy_args, source_files = _split_source_files(other_args)
 
-    if hook_args.fix:
+    if (
+        hook_args.fix
+        and "-fix" not in clang_tidy_args
+        and "-fix-errors" not in clang_tidy_args
+    ):
         clang_tidy_args.append("-fix")
 
     # Parallel execution is unsafe when arguments include flags that write to a

tests/test_clang_tidy.py

@@ -335,6 +335,7 @@ def test_fix_flag_appends_fix_to_command():
     ):
         run_clang_tidy(["--fix", "-p", "./build", "dummy.cpp"])
 
+    mock_exec.assert_called_once()
     cmd = mock_exec.call_args[0][0]
     assert "-fix" in cmd