But if the SVN repository is still active, then you would need to use git svn, as described in this article, in order to do git svn fetch / git svn dcommit. push the new Git repository to a new upstream repository hosting service. The account config dialog in SourceTree still suggests that SourceTree uses the key stored in the id_rsa file, but apparently it uses the one that is references in the. use SubGit to make a one-time conversion between the local SVN repository and a new local Git repository. ssh folder: # - Sourcetree Generated -Ĭhange the IdentityFile entry to point to your SSH key file It also adds a new entry to the config file in the. SourceTree will generate a new key pair and store it in your. The "Copy to Clipboard" button will change to "Generate Key"Įnter a passphrase and allow SourceTree to alter your SSH config In the configuration dialog press the Option-Key. Run SourceTree, go to "SourceTree" -> "Preferences" -> "Accounts" and select the account that you want to alter There seems to be no obvious way to select a different SSH key that you might have already generated by yourself.īackup your SSH keys and config files that are located in ~/.ssh/ In SourceTree if you enable SSH as an authentication protocol for accessing your bitbucket account the configuration dialog suggest that you use the id_rsa key that it apparently found in your. Step 1: Prepare the Subversion author list map file for Git usage. Checkout the trunk branch in the converted Git repo. Convert the Subversion repo to a Git repo. Here is how I managed to get this working: Here is how I use it: There are two initial major steps and one after-conversion step: Map the authors from Subversion to Git format. So, you have created your own SSH key pair and put the public key in your Bitbucket account at as described here:Īnd now you want to use that key with SourceTree on macOS. Sourcetree Get started Install and set up Sourcetree Install Sourcetree Step-by-step instructions for installation.
0 Comments
Leave a Reply. |