- Status:Closed(View Workflow)
- Fix Version/s: None
- Labels:
A free Git client for Windows and Mac Sourcetree simplifies how you interact with your Git repositories so you can focus on coding. Visualize and manage your repositories through Sourcetree's simple Git GUI. Added support for Visual Studio 2017; 1.30 Release Notes. Added support for private Bitbucket hostings. Added filtering/sorting/grouping repositories. Added using default repo path from Visual Studio user settings. Added an option to change a source branch when creating a pull request. 1.31, 1.32 Release Notes.
Install and set up Sourcetree. Install Sourcetree. Step-by-step instructions for installation. Connect your Bitbucket or Github account. In this course, learn how to use Git, the preeminent source code control software, which is a natural fit with and fully supported by Visual Studio. Jesse Liberty helps to simplify what can be an unwieldy concept by tackling Git from the ground up, and doing so in the context of a tool: SourceTree. Git config -global merge.tool sourcetree Now, git difftool and git merge commands will launch Visual Studio. Doing so is of course perfectly possible even without SourceTree. Just add the difftool and mergetool entries to your.gitconfig file (it should be located in your home folder) and execute the two git config commands shown above.
- Feedback Policy:We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.
Visual Studio 2015 currently only supports https or http transport. Thus, a repo must use http/https when the Team Explorer in visual studio is used to interact with a bitbucket repo.
When a bitbucket server has SSH enabled, the 'Checkout with Sourcetree' option always attempts to use ssh which then fails to find the existing repo in the Sourcetree URL action handler.
It would be nice if the Sourcetree url handler was somehow provided both available URLs by bitbucket and it could then choose the appropriate one given it's known repos. Lacking that, perhaps a per-project or per-user configuration that specified the preferred url scheme for sourcetree actions initiated from bitbucket.
Lack of this feature makes it hard for me to argue to visual studio users to migrate to sourcetree/bitbucket as once they configure visual studio to work these bitbucket actions are broke.
Attachments
- checkout-branch-in-sourcetree.png
- 19 kB
- sourcetree_integration.png
- 34 kB
BSERV-7734Choose protocol to use for checkout in SourceTree
- Gathering Interest
- Votes:
- 0Vote for this issue
- Watchers:
- 2Start watching this issue
- Backbone Issue Sync is enabled for your project, but there is no synchronization info for this issue.
If you want to access GitLab via SourceTree, you can connect it with an account profile now. Another method is to connect GitLab by using the clone function with SSH key.
What Will We Learn (Method 1)
Sourcetree Visual Studio Code Diff
- Access GitLab with personal access token
What Will We Learn (Method 2)
- Create SSH key
- Access GitLab via SourceTree with SSH key
Method 1: Connect with Remote (Account Profile)
Since SourceTree 3.0, it adds support for additional remote hosting services. They are GitHub Enterprise, Microsoft Visual Studio Team Services, and GitLab (Cloud, CE, EE).
Create Personal Access Token
To connect GitLab with Remote, personal access token is required for authentication. To create personal access token, login GitLab and go to Settings.
After that, select Access Tokens from the sidebar. You will create your personal access token here. Give access token a name. You are able to set an expiry date for your access token. By leaving it blank, access token will never expire. Next check the api and read_user checkbox, it is required for SourceTree to connect to GitLab remotely. Click on Create personal access token to complete the setup.
Next open up your SourceTree, click on Remote and click on Add an account.
Select GitLab as the hosting services, and choose HTTPS as the Preferred Protocol. Click on Refresh Personal Access Token.
You will be prompted to enter the username and password. After entering the username and password then press OK to continue.
Do take note that email address you used to login GitLab is not your username. If you do not know your username. Go to GitLab and click on the top right profile icon. The text after @ is your username. In this example, it would be aword-test.
Furthermore, the password is your personal access token code. It only shows you once you created your personal access token. Make sure save your personal access token code in a safe place.
Then you have completed the steps to connect GitLab with SourceTree. If you connect successfully, you will able to see your repositories in SourceTree.
Method 2: Connect with SSH Key
This method is useful for users who are not using SourceTree 3.0 and above.
What is SSH Key
The Secure Shell (SSH) key is based on the principle of Public-key cryptography. It is used as a way of authentication. By generating an SSH key pair, you will get a private key and a public key. You can image public key as a padlock. You can distribute it to any systems on the Internet. Private key is like a key of the padlock. You should keep the private key securely and avoid it from being compromised. To access any system with public key, you need to use the private key to authenticate yourself.
Create SSH Key
To create SSH key, you need to generate your own SSH key with SourceTree. Go to Tools and select Create or Import SSH Keys.
Click on Generate to create SSH Key. Move your mouse cursor within the PuTTY Key Generator continuing to generate the SSH Key.
After SSH Key is generated, type your own Key passphrase for your SSH Key. Key passphrase is like a password to protect your SSH private key. Save your public key and private key for future use.
Add SSH Public Key to GitLab
To add your SSH Key to GitLab, you need to log into you GitLab account. Click on your profile icon on the top right corner, then select Settings. Click on SSH Keys on the side menu.
Copy your public key inside your PuTTY Key Generator, then paste it into GitLab. Click on Add Key to add your SSH Key into the GitLab.
Add SSH Private Key to SourceTree
To add private key to SourceTree, Click on Tools then click Launch SSH Agent…
You will find SSH Agent named as Pageant on the taskbar. Double click on Pageant.
Now click on Add Key. Add your private key which have been saved earlier.
![Sourcetree Visual Studio Sourcetree Visual Studio](/uploads/1/3/7/3/137352117/330726571.png)
Clone Repository to Access GitLab via SourceTree
Sourcetree Visual Studio Authentication Failed
Go into your projects in your GitLab. Copy the SSH URL.
Sourcetree Visual Studio Download
In SourceTree, click on Clone. Paste the repository URL into Source Path. Click on Clone, you have successfully connected GitLab with SourceTree. Now you are able to pull and push your code to GitLab with SourceTree.