What is wrong with spawning of githooks?

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

My shebang looks as following: 

':' //; 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


1 answer

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

The right answer is available here:


Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Published Jan 23, 2018 in Sourcetree

Tip from the team: workflow and keyboard shortcuts

Supported Platforms macOS Sourcetree has a lot to offer and, like many developer tools, finding and using it all can be a challenge, especially for a new user. Everyone might not love ...

800 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you