git pre-commit hooks

[a-sevin]

GIT can provide tools to check / lint the code before creating a commit. We are using it in our simulation project COMPASS and I find it very useful.
So, I have several questions regarding hooks:

1. Do you think it's useful?
2. If yes, which tools to you want to check:
   a. lint: removes un-useful CR, white spaces, format the code with tools like astyle, clang-format, ...
   b. static analyse with cppcheck
   c. other in mind ?

If you want, I can put it in my branch and try it before adopting it (or not)

Cheers,

Arnaud

[oguyon]

yes, that would be super useful. I have no experience using these tools, so I defer to your advice about which one(s) to deploy With multiple potential contributors, these tools will help manage / homogenize code On Dec 17, 2017 22:53, "Arnaud Sevin" <notifications@github.com> wrote: GIT can provide tools to check / lint the code before create a commit. We are using it in our simulation project COMPASS and I find it very useful. So, I have severals questions regarding hooks: 1. Do you think it's useful? 2. If yes, which tools to you want to check: a. lint: remove unseful CR, white spaces, format the code with tools like astyle, clang-format, ... b. static analyse with cppcheck c. other in mind ? If you want, I can put it in my branch and try it before adopt it (or not) Cheers, Arnaud — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <milk-org/milk#2>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFVuDahMNIviCcowsvgA9CNartaF5LFqks5tBifwgaJpZM4RFJX8> .