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.
Use sourcetree windows#
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 kommentar(er)
