Fix minor issues with clang-tidy workflow #79234
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
None
Purpose of change
This is a followup to #79100
@akrieger brought up two issues with the change in #78801 (comment)
LOCALIZE=0
makes clang-tidy complain about every use of_
, among others.More generally speaking, it's probably worth it to have the stock scripts run as close as CI as possible
Describe the solution
TILES
andSOUND
switch from0
to1
don't rebuild compilation database if it already existsforce-overwrite the compilation database if it exists (local runs were failing on me trying to symlink the already exiting one)Describe alternatives you've considered
Testing
CATA_CLANG_TIDY=clang-tidy-17 ./build-scripts/clang-tidy-run.sh
with no extra args works for me locallyOn this PR, before I un-drafted it, here's the job that properly skips attempting to download the plugin: link
Additional context
This is mostly unrelated and a problem for another time, but
skip_duplicate check actually doesn't do what we want it to do. For example it thinks that CMakeLists.txt changed in this JSON-only PR: https://github.com/CleverRaven/Cataclysm-DDA/actions/runs/12826245046?pr=79204
This is because it checks the difference between the branch base and the merge pr, which includes all the other changes between when the branch was created and now.
skip_duplicates also can fail the other direction too. For example the intent is there for draft prs to not trigger clang-tidy checks. However that means that one can create a draft PR, skip clang-tidy checks, and then un-draft it, and skip the checks again because
skip_duplicates
treats it as a duplicate (see this check on this PR itself https://github.com/CleverRaven/Cataclysm-DDA/actions/runs/12848556910?pr=79234)Now, we are also not abiding to what
skip_duplicates
tells us to do, because (i think) it sets theshould_skip
to"Yes"
and we later check whethershould_skip == "true"
and assuming we should never skip things... (see last link above again)This is all rather broken overall...