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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


BUG: "problem opening this repository" using iTerm2 as terminal app

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Jun 09, 2023

I'm running SourceTree 4.2.3 (252) on a 2023 M2 Mac mini under Ventura 13.4 with iterm2 3.4.19 installed.  I've been into SourceTree > Settings > General > Miscellaneous > Terminal app and selected "iTerm2" from the list.

If iTerm2 is already running then clicking the "Terminal" button on the SourceTree toolbar works as expected - a new iTerm2 window opens up and runs a "cd" command to get to the repository clone's gitroot directory.

However, if iTerm2 is not running, I get a popup dialog saying "There was a problem opening this repository in iTerm2".  iTerm2 is launched and a window opens, but there's no "cd" command, so I guess there's a timing problem in passing that string to the shell if the app is only just starting up.

I can work around this by going to iTerm2 > Settings > General >Closing and unticking "Quit when all windows are closed".  That way iTerm2 keeps running after I've tidies up all my various windows, so it's ready and able to take the "cd" command at launch from SourceTree.

1 answer

0 votes
Arati Mohanty
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 09, 2023

Hi @kmbro We understand the problem caused and also able to reproduce it in our environment. We will work on it and let you know the updates.

As with the work around, it is working fine we consider this is not blocking you from using SourceTree.

Also, We request you to kindly raise a bug at!default.jspa . This will help us to track the issue better.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events