jrtom/jung

Consider using pre-commit or equivalent to prevent unformatted (and untested?) code from being checked in

Opened this issue · 3 comments

This issue is a follow-on to #214 (comment)

@jrtom Out of curiosity, do you use any tools at Google, internal or otherwise, which prevent code from being checked in at the client side before tests/checks pass? If these tools are open to non-Googlers, could we use them instead of pre-commit?

This also makes me want to ask: are there any other tools and development practices you take for granted at Google that we could aim to incorporate here or find alternatives for to make GitHub a more pleasant experience?