-
Notifications
You must be signed in to change notification settings - Fork 50
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
Add check format local #490
Conversation
71f52c4
to
f9974e5
Compare
f9974e5
to
46f006b
Compare
@paulgessinger I have question: There is the line in traccc/.github/check_format.sh Line 36 in a217af7
If I run this with
I think I have seen this in Acts core as well, do you know how to bypass this? (Maybe adding an |
@beomki-yeo I guess it depends if the mounted volume has |
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.
I don't know... I see that this can help people in some situations, but...
On your personal machine you can just install clang-format
, and in 99.999999% of the cases it will just work fine with the check_format.sh
script. I didn't yet run into a situation where clang-format
on Ubuntu 20.04, Ubuntu 22.04 or RHEL9 would not have produced the same output as clang-format
in the specific Docker image that we use.
And for the very-very rare cases where this happens, I'm okay with just starting Docker myself. 🤔
If we want to make this script "a thing", it would have to be smarter than this. Right now I can just start it from a "wrong directory", and it will not work.
So... do we really want to write a script like this? Because then it would have to be made a little more robust than this...
Have you tested with other version of clang-format? |
|
As I wrote, on Ubuntu I only ever installed the default Admittedly I apparently spoke too quickly about RHEL9. Apparently on that I only ever used the Docker image. As I'm having a hard time finding a viable package for it on a vanilla system. 😦 But what always works for me, even on Windows: VS Code comes with a built-in code formatter. Which respects the project's |
For people who don't have clang-format-10