Use a clang-tidy configuration file

[IAmNotHanni]

Discussion: #484

This uses a .clang-tidy configuration file to specify which warnings to ignore and which files to analyze.
Please check the result of the CI log before merging this, I can't test it in my fork.

[adam-sawicki-a]

Works fine.

I would also like to disable:

invalid case style for variable 'VMA_SUBALLOCATION_TYPE_NAMES' [readability-identifier-naming]

warning: parameter name 'v' is too short, expected at least 3 characters [readability-identifier-length]

[adam-sawicki-a]

I can see file /home/runner/work/VulkanMemoryAllocator/VulkanMemoryAllocator/build/CMakeFiles/3.31.6/CompilerIdCXX/CMakeCXXCompilerId.cpp is still analyzed.

[IAmNotHanni]

I can see file /home/runner/work/VulkanMemoryAllocator/VulkanMemoryAllocator/build/CMakeFiles/3.31.6/CompilerIdCXX/CMakeCXXCompilerId.cpp is still analyzed.

In b5a5703 I changed it so it ignores the build directory. It should work now.

[IAmNotHanni]

It works, but I get the impression that it does not analyze the files of the sample app, only vk_mem_alloc.h.

[IAmNotHanni]

(I will have time to fix this sunday evening, need to go)

[adam-sawicki-a]

Now we have a lot of warnings coming from analysis inside of Vulkan SDK, like "/home/runner/work/VulkanMemoryAllocator/VulkanMemoryAllocator/vulkan_sdk/1.4.309.0/x86_64/include/slang/slang-com-ptr.h" 😟

[adam-sawicki-a]

I can't test it in my fork.

Why can't you test GitHub Actions on your fork? It seems to work for me. I created a fork on my GitHub account:
https://github.com/adam-sawicki-a/VulkanMemoryAllocator/tree/master
And also on my another (personal) GitHub account that has no write access to the original VMA repo:
https://github.com/sawickiap/VulkanMemoryAllocator
I can see all actions executed on both of them.

[IAmNotHanni]

Now we have a lot of warnings coming from analysis inside of Vulkan SDK, like "/home/runner/work/VulkanMemoryAllocator/VulkanMemoryAllocator/vulkan_sdk/1.4.309.0/x86_64/include/slang/slang-com-ptr.h" 😟

Interesting 😄

I can't test it in my fork.

Why can't you test GitHub Actions on your fork? It seems to work for me. I created a fork on my GitHub account: https://github.com/adam-sawicki-a/VulkanMemoryAllocator/tree/master And also on my another (personal) GitHub account that has no write access to the original VMA repo: https://github.com/sawickiap/VulkanMemoryAllocator I can see all actions executed on both of them.

I honestly don't know. I will try to get it to work first before pushing further commits.

[IAmNotHanni]

I can't test it in my fork.

Why can't you test GitHub Actions on your fork? It seems to work for me. I created a fork on my GitHub account: https://github.com/adam-sawicki-a/VulkanMemoryAllocator/tree/master And also on my another (personal) GitHub account that has no write access to the original VMA repo: https://github.com/sawickiap/VulkanMemoryAllocator I can see all actions executed on both of them.

What you see in your fork there is the CI from the last merge. Since this account of you is not owner of VMA repository, it is not allowed to run the CI I think. If you would make a commit into the fork, I think GitHub won't permit you to run the CI in that fork. Since it's even with master branch, it just shows the last CI run from VMA repo's master branch.

[sawickiap]

I still think it works. On my personal GitHub account I created a branch of my fork:
https://github.com/sawickiap/VulkanMemoryAllocator/tree/CI-test
I introduced a bug:
sawickiap@98c26cb
And I can see the CI build failed:
https://github.com/sawickiap/VulkanMemoryAllocator/actions/runs/14497422259/job/40668587636

[IAmNotHanni]

Interesting. I will try to get it to work for my fork.