2

Disclaimer: yes, I've read Skip Git commit hooks and I know about the -n flag, but this is not what I'm looking for.

I have that pre-commit hook that runs in order to do some code prettifying (replace tabs with spaces, remove double empty lines, ...).

However, there are some use cases where I don't want the hook to run: for example, when I'm checking in some Makefiles, I cannot simply replace tabs with spaces, so I'd have to skip these files.

If I were the only developer, I would be fine with the -n flag in order to prevent the hook from being run, but there are other guys that use UIs that don't know the -n flag (cough tortoisegit) and they won't be willing to specify some flags to commit.

Apart of implementing the skipping directly in the hook and the obvious -n way: are there any other ways how I could prevent the pre-commit hook to be run?

Community
  • 1
  • 1
eckes
  • 64,417
  • 29
  • 168
  • 201
  • Why not implement it in the hook? That would make it more portable *and* not rely on every user having Git setup to accommodate your not particularly well-written hook. – Biffen Mar 31 '14 at 13:31

1 Answers1

4

Following a similar idea as this pre-commit hook, you could use:

git diff --cached --name-only

That would list the files that are about to be committed, and you can then filter on them in order to apply your controls or to skip those files.

In other words, the hook is still running on every commit, for every files.
But its script is smart enough to apply its test to the right files within the list of files to be committed.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250