Open System Preferences, select the Keyboard option, then the Shortcuts tab, followed by the App Shortcuts menu item. Identify the menu item that either has no keyboard shortcut, or one that you don’t like, and take note of its name. Sourcetree is no different than any other Mac application, in that you can define your own keyboard shortcuts for system menu items. Open file browser (fastest way to switch repositories) These are the Mac keyboard shortcuts (although I suspect the Windows equivalents are more often than not, the same but with ctrl instead of cmd). So I’ll repurpose this blog post instead to surface some of the more useful keyboard shortcuts (this list is no longer exhaustive), and explain how I extend the keyboard shortcuts Sourcetree provides natively. Now, in 2020, the keyboard shortcuts are readily available both in-program (on each context menu item) as well as a few easily located resources online. Originally (back in 2015) this post was a record of my attempts to brute force the discovery of Sourcetree keyboard shortcuts, because they were not well-documented by Atlassian (or anyone else I could find at the time). I mean that copy-pasted token.Atlassian, efficiency, keyboard shortcuts, sourcetree, version control Congratulations !ġ4- Do not forget to remove the TEMPORARILY saved token (if you saved it somewhere) which can be stolen and used to access your account. That is why we saved the token temporarily.ġ3- Fetch your repos, it should work now. You might get the same window when you Fetch anther repository. )ġ2- You will notice a new password window shows up asking for password, Enter the same Token which you used it earlier. You can go again to Authentication of SourceTree and see your account has actually been added !ġ1- Ensure that your repository setting of your git is correctly formatted (. It will tell you it failed, do not worry it did not !Ĩ- Click Ok then Close SourceTree Completely.ĩ- Remove the password cache file called "passwd" in "C:\Users\\AppData\Local\Atlassian\SourceTree".ġ0- Open sourcetree again. Ensure you have this token saved somewhere TEMPORARILY because we will need it.ħ- Enter your email as username, and the just generated PAT as password. It is your decision !Ĥ- Open SourceTree, go again to Tools -> Options -> Authentication.Ħ- Prepare your new Personal Access Token, then click "Refresh Personal Access Token" button. Currently it is possible to return back to old format. So, if you want to follow exactly what I did, do it. I closed Visual Studio as well, just in case !ģ.5 - I switched to DevOps format from Organization settings in DevOps website. I am using SourceTree for Windows version 3.2.6Ģ- Remove all Visual Studio (or DevOps). You will try, and think you are not successful, but you are really near from it ! follow with me: I can use this to add my repos as remotes and my old, carry-over authentication still works for old repos. It popped up a login field I entered my email as user name and the PAT password as my password and after a while it came back Authenticated. The only flaky part was actually clicking the button to activate the Personal Access Token I had to make sure the Host URL field didn't have focus (I clicked every field in order, top to bottom to make the PAT button work). I added a new account to Authentication and used the built-in Azure option and the ` ` URL for the Host. The Azure integration seems to be working okay now. If, like me, you regenerated your token you use for SourceTree so you could get the password, you will need to edit the DevOps remotes and select the new DevOps Host entry instead of the old Generic Host. Remotes will work fine with the format after this initial account authorization.Īny remote repository added using the old Generic Account / Generic Host method (3.1.3 on Windows still had no DevOps integration) should still work if you didn't regenerate the token those remotes use. When trying to authorize with, it seems to succeed in logging in, but fail at gaining Git permissions. This is still the case in the SourceTree 3.2.0 Windows beta that is only a few days old. There is an open bug report on it (as Christian Wölke pointed out quite some time ago) that seems to be getting some slow progress, but a bump could help reminding them that it's still an active issue: When using this as host URL, and then using the account name used to log in DevOps as username and the PAT as password, it's working.Įdit:As of the issue is still ongoing, and I see more people are finding the answer here. One should still write it in the old VSTS link format (even if the organization has been made on DevOps): Please give this a go, before trying the workaround!Īpparently (at the time of writing ), when writing the host URL rather than writing: Edit: (as of ) The issue is reported as resolved - see
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |