Describe the bug
When changing a single file, all files, even those that aren't dependent on it, will be reanalyzed
You can make sure all files have been reanalyzed by adding the --subcommands parameter to your bazel command.

Versions

• CodeChecker: 6.26.0 (0bbf351e870c7056cd9cc0dc44a795c0fe805dfa)
• bazel: 6.5.0

To Reproduce

• Run the per-file analysis
• Change one file
• Run the per-file analysis again

Expected behaviour
On the second run, most files should not be reanalyzed; their result should be cached.

Additional context
Logically, the problem should be that for every analysis job, the input list is every file in the project, and Bazel decides which actions it should re-run solely on the input files.