Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,856
Community Members
 
Community Events
176
Community Groups

env: node: No such file or directory

Every time I try to  commit, pull or push SourceTree app prompts this weird error. 
 
It started happening when I have changed my default node version on my NVM (node version manager) on my Mac.
Screen Shot 2016-01-20 at 10.04.01.png

Git works just fine from the command line. So it is only on SourceTree
 

4 answers

The right answer is available here:

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

Run "/Applications/SourceTree.app/Contents/MacOS/Sourcetree" from terminal instead of running launcher. It works for me. Found the solution on stack overflow

Hi yes. @Dhairya Dhairya, it was my git hooks - i had custom git hooks that did check lint before allowing commit. Source tree couldn't handle custom feedback.

I removed all custom git hooks to fix this. Which was technically not solution, since I had to check linting manually. Source tree actually got to me. 

I switched to CLI git and started using "GitKreken" (pretty intersting ui). 

@Nerijus Gudas any luck to solve this? Currently, i am facing this problem too.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events