What is wrong with spawning of githooks?

[Dmitri Shchurov]

I've got the following output .git/hooks/pre-commit: line 2: exec: : not found

My shebang looks as following: 

#!/bin/sh
':' //; exec "$(command -v nodejs || command -v node)" "$0" "$@"

Being running, the script works fine. When I try to commit my changes, I get the error.
I also tried another shebang

#!/usr/bin/env node

with the same result (node not found).

I could try to solve this with a soft link to node as '/usr/bin/node', but I'd like to avoid doing this.

Node is installed and is managed with nvm. And nvm alias to stable was made, and node is available in all shel command windows.

I'd like to know the way SourceTree spawns githook commands. 

PS $git commit itself works fine, githook script is processed without errors

[Pulkit Singhal]

If `nvm` is what takes care of your nodejs installs, then:

The right answer is available here:

https://answers.atlassian.com/questions/140339/answers/32030983