Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it good form to scrub development code from my source files during a pre-commit hook?
For example, I have code that is calling xdebug_break() and I want to remove the calls to that function from any files that have it before committing my code to the repository. I would rather not check for the function before calling it because I am the only one that wants that function call there.
It’s ok to have the precommit hook modify code before committing it. For example, a development team might use the precommit hook to automatically reformat any code that is committed to automatically enforce that team coding conventions.Based on the comment, I’m changing my answer – the svn manual specifically recommends AGAINST changing the contents of a commit because it can screw up the client side caching. Git works differently since the repository is local, but I guess the principle is the same.
As for the specific use case that you mentioned; it does seem a a little unconventional to use the precommit hook for that. Typically, the precommit hook is used for more general purposes. That said, if you’re the only developer, you’re free to use it however you like. Just don’t forget that it’s there.