Here's a picture of what I'm referring to:
How do I get rid of this warning symbol? If I click on it, I get the message "You don't have any remotes which have extended integration settings configured; you need to edit your remotes to add details such as the hosting type and base URL. Click the Settings button to open your remote list".
If I do just that and edit my origin remote, the only host types being offered are BitBucket, GitHub and Stash - none of which my project is using, so I can't actually do what I'm asked.
Anyway, why do I need to add a hosting type? This seems like a new feature that'd be convenient for a lot of users, but not something essential. Why throw a big red warning sign at me over this - making it the center of my attention for up to an hour now - when nothing is actually wrong?
I don't want to use extended integration, I just want to get rid of this warning sign because it's a major distraction.
It's basically the same issue as the constant "Git LFS is not supported" nagging when I don't use Git LFS, but at least you could dismiss those messages. This one doesn't seem to want to let go, ever.
Maybe allow people to pick "Other" or "not on list" or something so you can take suggestions for other systems (if they exist?) or just go away for sites that are hosted locally!? I mean GIT IS a distributed source control system... so why suddenly do you think it NEEDS a central server and what's worse is one you deem worthy? ;p
Yes and I love and worship it for that stuff! 🙇♂️Please don’t think otherwise! It’s amazing for a paid app never mind free!
BUT the red exclamation I can’t “fix” for other stuff without a server is making my brain twitch! 🤪 LOL
Just the ability to say “yes thanks I know” for a repo would solve it.
Yes, please fix it with the softening you describe! Thanks.
Until then, this bug looks VERY BAD when I demo SourceTree to colleagues in hopes of convincing them to use it - a big red exclamation that cannot be fixed makes prospective new users nervous! They think something is actually wrong, and are not comfortable enough to start trying SourceTree out for themselves.
This makes SourceTree look bad!
UPDATE: This seems to have been fixed (at most with 3.1.1). Thanks!
I had the same issue and was able to fix it by recreating my origin:-
Go into Repository/Repository Settings, select your origin & edit.
In my case I made a not of the URL then removed the origin then re-created it with the same URL and I also had to change the remote account in Optional Extended Integration from Generic Host to my Bitbucket Server.
Hope that helps.
Also just upgraded to 3.3.4 and began receiving the Exclamation Mark of Impending Doom.
Interestingly when I click it I get a message from windows telling me I need to get an app from the app store to open an ssh link.
I seem to be able to fetch from the repos without issue. We have Bitbucket server as our main repository, and as you might guess from the above error, I use ssh to connect.
Deleting and recreating the "Remote Repository Path" from the Repository settings (as suggested by mbandy) did not help.
I was able to get rid of the E.M.o.I.D. by going into the Repository settings and changing the Host Type from "Unknown" to Bitbucket server and putting in any URL at all. I even tested "http://fake.com/" and the E.M.o.I.D. goes away.
That being said, it makes the button worthless. I was able to get the button working by going to my Bitbucket server and getting the clone URL, specifically the HTTP clone URL, not the SSH url and using that without the final slash and repo name (ie the clone URL of "https://a.b.com/abc/my/repo.git" becomes "https://a.b.com/abc/my". With that setting the "Remote" button opens a browser directly to my Bitbucket server project.
Hope this helps someone.
Over a year and a half later and this clearly defined bug with a huge annoyance level and high number of impacted users remains a problem. It's quite shocking and even a bit concerning about the Atlassian ecosystem as a whole. I mean... if they have such trouble solving such a clearly defined issue... I just don't know...
Further, I know ST is a free product but it sure would be nice if those of us who actually pay for Atlassian's other products didn't have to go elsewhere for a Git client because of small bugs that the company won't prioritize.
I upgraded to 3.3.4 this morning and got the red exclamation mark. After searching through the above threads, I went to the main menu "Repository" item, selected Repository Settings and selected my repository origin (we have a private Bitbucket server).
I clicked "Edit" and then under Optional Extended Integration selected Bitbucket (it was set to Unknown or whatever the default was before). The red exclamation mark went away.
Just FYI I've been pretty happy with Sourcetree so far.
I hadn't noticed it because I typically only start Sourcetree after rebooting my machine, which usually only happens when IT decides to periodically "re-educate" my laptop :) Otherwise I just hibernate instead of shutting down.
Mostly just a cosmetic thing, but the red color could be alarming to users. If I had serious OCD it might actually bother me ...
Are we dealing with more than one issue here?
In my case, I get the exclamation point and it is fixable in the way others have described (except the fix only lasts until the next restart of the program). However, the issue is only cosmetic as the program still seems to work regardless of whether I have the exclamation point or not. It seems like, perhaps, for others the exclamation point also implies a non working state making the issue different than what I am seeing.
Or are we dealing with one issue that manifests in two different ways?
I should note, however, that at one point I did have a functional issue. I kept removing things in windows that seemed related to Sourcetree authentication until Sourcetree started working. However, as I noted, the exclamation mark issue did not go away (though I don't much care as long as pushing and commit work).
Agreed. I'm still using 3.3.4 (have not been prompted to upgrade in a long time) and still use SourceTree all day, every day. Works fine for me, and saves a lot of typing over having to use Git Bash :)
That said, I read somewhere that later versions might have other issues. Maybe that is why I have not been prompted to update yet ? Are there "stable" vs. "development" versions that people are using ?
Considering all the other problems I have to deal with on a daily basis this seems like a pretty small issue.
About a week or so ago I noticed that I couldn't fix the red exclamation mark anymore, running 3.3.8. I just upgraded to 3.3.9 this morning, and the same thing.
The repository settings show the repository as "Generic", and there is no choice for Bitbucket. Hmm ...
That said, I know IT upgraded our Atlassian server software recently -- we got new goodies in our pull requests, for example. Maybe there is some kind of server incompatibility with 3.3.9 ?
I still consider this to be cosmetic, and I bet if the color wasn't red almost nobody would notice it.
It is not "cosmetic" at all for me. Until I change the "Optional Extended Integration" account to my BitBucket account, simple git operations work but I can't initiate a pull request (from within SourceTree).
True... the workaround isn't complicated, but it's very annoying that Atlassian is taking so long to do nothing about what seems to be a clearly defined and very annoying bug.
Interesting, I've never actually done a pull request from Sourcetree before -- I just use our Bitbucket server for that.
So I tried it -- I right-clicked on a branch, and selected "Create Pull Request ..."; it came back with a dialog which said I had to fill in the extended integration details under repository settings. I did that, set the type to Bitbucket Server, filled in the base URL with our corporate Bitbucket URL, and my username. The red mark went away. Okay, good !
Then I was able to do the pull request, BUT all it does is go to our Bitbucket site and do the couple keystrokes that I would have done manually. That is kind of neat (but it's hardly a miraculous time-saver).
And of course the settings do not persist, once entered. That is a little annoying. I'll llive, though :)
Bug is seen.
TLDR; exclamation point goes away with this change but change does not stick after a restart.
Using 18.104.22.16848 here. Issue "goes away" after 'Optional extended integration' setting for remote account in 'Remote details' of repository paths from 'Repository settings' is set to "Bitbucket Server" instead of "Generic Host".
Exclamation point on button comes back after restart. Previously set setting is not sticky and can be seen to have reverted to "Generic Host". Despite this, pull & push functionality seems to work.
For me, it open a screen asking to select an app in the Microsoft Store with the message "you'll need an app to open this ssh link. Look for an app in the Microsoft Store".
Why it would do that I don't know. I would think whatever action the button is intended for, should be done from SourceTree? Like open the Repository Settings dialog maybe.
same problem here. Just upgraded to 3.3.4 and the remote icon is showing exclamation mark.
When doing the following steps the exclamation mark goes away but restarting sourcetree gives the same problem.
Even with the exclamation mark everything seems to be working fine but it's annoying.
I'm still debating whether to rollback to 3.2.6 or not. The upgrade to 3.3.6 (then 3.3.8) was a disastrous experience:
- Display that is not refreshed anymore (SRCTREEWIN-12705, fixed in 3.3.8)
- Open Terminal not working anymore (SRCTREEWIN-12853, fixed by upgrading git from 2.21 to 2.25)
- Crash every time I clone a new repo (still not fixed).
- Repo config that is lost every time SourceTree is restarted so I have to reconfigure as a BitBucket server every time (related to SRCTREEWIN-10820)
I have experienced all the same issues as @Jasmin Letendre mentioned above. I also experienced an issue where when cloning our master it threw errors due to file name length. So, I had to go into GIT BASH and override the filename length to get it to correctly clone the master.
For what its worth -
Just to update - The red exclamation marks do not appear in two of my other machines running Sourcetree versions: 22.214.171.12439 and 126.96.36.19929
I "Checked for updates" under options to update the Sourcetree but gives me a green light saying "Sourcetree is up-to-date". Why is it not picking up the update for 3.3.8? (Probably better that way)
I suspect the auto-update feature of the software may be broken as well?
I have not seen any updates for some time, and I am running version 3.3.4.
That is not the latest version, as far as I know.
However, in the about screen there is no "Check for updates button" anymore.
So the only way to check for updates is apparently to download the latest manually.
The issue with the red exclamation mark has now persisted since late 2018.
I am not sure Atlassian is actually fixing any bugs in their product currently?
I didn't try but I guess there isn't a fix for it
OK. I shot them a Twitter message regarding this thread and got this back -
"Hi Deepak - thanks for getting in touch with us. We've reached out internally for some additional insight from our team, and will circle around with any updates! Appreciate it. -MP"
Hope there is a solution to this annoyance soon.
I found the solution by going back to 3.2.6. This is the version where red exclamation mark disappears. This is the version where subtrees tab does not disappear every time you close the program. I have tried all versions one-by-one. I believe, 3.2.6 is the last-good-standing version from many perspectives. I am not sure if a feature added after this version is vital for your work or not. But I would recommend you to look at this version and see if this works for your.
Seems like Atlassian does not update the windows version anymore.
I can confirm that with the update to 188.8.131.52, my red exclamation is gone. The red exclamation seems to appear when I open the repo and the remote account is selected to Generic or using different account to authenticate.
Once the authentication account matches the remote account, the red exclamation goes away. This was the case previously as well but it was not persisting the change in account selection. With the new update, it seems to persist the account setting for individual repos and hence the red exclamation goes away.
Please check your account setting under Repository settings > Remote repository paths > Optional extended integration> Remote account
Hope this helps.
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events