-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
3.0.8
-
Windows 10 Pro v1803 build 17134.345
-
Severity 3 - Minor
See also SRCTREE-6139 (where this was originally misreported as a Mac issue).
As originally reported by Attila Tamas Zimler :
"The private remote SSH access is not expected to have remote details beside the origin path, so the optional extended integration is not configured. However, because no configuration for it, the Red exclamation mark does not disappear. Which in turn, is irritating."
The problem with this UX is that it is giving the false impression that something is wrong that the user needs to correct, and obviously there is nothing to correct.
- is duplicated by
-
-
- Closed
-
[SRCTREEWIN-10820] Source tree remote settings are displaying a red exclamation mark - for private SSH remote access
I can confirm that this is back in 3.3.4 and it's very annoying.
This is not an "error", it is perfectly normal for many, perhaps most businesses which run their own Git server. Please remove the exclamation mark, which is back in 3.3.4 and is still incredibly annoying. Perhaps you forget how "attention-to-detail" oriented your user base is.
Work-around
1. Close Sourcetree
2. In the project's local .git directory, edit the file sourcetreeconfig.json as follows:
Replace:
"RemoteProjectLinks": []With:
3. Restart Sourcetree
On inspection you will notice that RemoteProjectLinks will be further populated automatically with additional fields that are mainly nulls.
This change had no negative impact on the use of Sourcetree to interact with local repository servers, but had the positive impact of removing that annoying misleading red exclamation badge.