-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(ci): change pre-commit clang-format to run in ci [skip pre-commit.ci] #1373
base: main
Are you sure you want to change the base?
Conversation
pre-commit.ci autofix |
Capybara summary for PR 1373 |
d4835cd
to
b441fe4
Compare
After squash merge, we should add the commit to |
b441fe4
to
882dc7d
Compare
eec5d39
to
fa0a080
Compare
clang-tidy error https://github.com/eic/EICrecon/actions/runs/8663802856/job/23763825088#step:9:120 is caused by the yaml file containing segments like: - BuildDirectory: /home/runner/work/EICrecon/EICrecon/build/src/utilities/eicrecon
DiagnosticMessage:
FileOffset: 0
FilePath: ''
Message: macro replacement list should be enclosed in parentheses
Replacements:
- FilePath: ''
Length: 0
Offset: 15074
ReplacementText: (
- FilePath: ''
Length: 0
Offset: 15088
ReplacementText: )
DiagnosticName: bugprone-macro-parentheses
Level: Warning where the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clang-Tidy
found issue(s) with the introduced code (1/1)
src/benchmarks/reconstruction/tracking_efficiency/TrackingEfficiency_processor.cc
Show resolved
Hide resolved
42e3312
to
2487714
Compare
d717216
to
928f37d
Compare
Rebased, no changes in these files.
667b8f6
to
928f37d
Compare
for more information, see https://pre-commit.ci
Briefly, what does this PR introduce?
We don't let the CI pre-commit job run automatic clang-format and cmake-format fixes. This PR changes that behavior for clang-format, by updating the clang-format pre-commit hook.
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
No changes.
Does this PR change default behavior?
Yes, it might lead to developers seeing their code reformatted automatically.