Skip to content

chore: fix all clang-tidy findings in the existing code - #86

Open
EnriqueParodi wants to merge 1 commit into
ci/release-changelogfrom
chore/clang-tidy-main
Open

chore: fix all clang-tidy findings in the existing code#86
EnriqueParodi wants to merge 1 commit into
ci/release-changelogfrom
chore/clang-tidy-main

Conversation

@EnriqueParodi

Copy link
Copy Markdown
Collaborator

The new nightly clang-tidy job runs over the whole tree; this clears every
finding its first full run reported, so the job is green from night one.
Where a check is wrong or the code is deliberate, the waiver is written
next to the code together with its reason.

@EnriqueParodi
EnriqueParodi force-pushed the chore/clang-tidy-main branch 2 times, most recently from 2a4b650 to 28f1641 Compare August 18, 2026 23:01
@EnriqueParodi
EnriqueParodi changed the base branch from main to feat/web-explorer August 18, 2026 23:01
@EnriqueParodi
EnriqueParodi changed the base branch from feat/web-explorer to ci/release-changelog August 18, 2026 23:15
@EnriqueParodi
EnriqueParodi force-pushed the chore/clang-tidy-main branch 2 times, most recently from e8d8ab2 to eb97dcf Compare August 18, 2026 23:19
@EnriqueParodi
EnriqueParodi force-pushed the chore/clang-tidy-main branch from eb97dcf to 70d99da Compare August 18, 2026 23:47
@EnriqueParodi
EnriqueParodi marked this pull request as ready for review August 18, 2026 23:49
@EnriqueParodi
EnriqueParodi force-pushed the chore/clang-tidy-main branch from 70d99da to 25add43 Compare August 19, 2026 07:42
@EnriqueParodi
EnriqueParodi force-pushed the chore/clang-tidy-main branch from 25add43 to f5c06f3 Compare August 19, 2026 12:18
@EnriqueParodi
EnriqueParodi force-pushed the chore/clang-tidy-main branch from f5c06f3 to a8ab214 Compare August 19, 2026 12:41
@EnriqueParodi
EnriqueParodi force-pushed the chore/clang-tidy-main branch 2 times, most recently from 35f6af8 to 28f731c Compare August 20, 2026 11:26
The new nightly clang-tidy job runs over the whole tree; this clears every
finding its first full run reported, so the job is green from night one.
Where a check is wrong or the code is deliberate, the waiver is written
next to the code together with its reason. It also carries the unused
variable removal from #63, which gcc-16 reports as an error.

Co-authored-by: Florian Sattler <florian.sattler@airbus.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant