Sourcetree With Azure Devops

Sourcetree With Azure Devops

We have an on-premises Azure DevOps Server and like to use the Git workflow 'Fork-Clone-Push-PR'. In the moment of forking the system let allow us decide into which project and under which name the repository should get forked. Forking it in the same project would mean tons of such forks after a while, which looks ugly. SourceTree can be used by both Mac and Windows users on your team and makes your team talk in the same GIT lingo and use Git WorkFlow. Whereas Azure DevOps lets you work on your product in an Agile.

  • Status:Needs Triage(View Workflow)
  • Resolution: Unresolved
  • Fix Version/s: None
  • Labels:
  • Environment:

    Sourcetree Version 3.1.3

    Operating System : Windows 10

I have latest Source tree 3.1.3 on windows 10 , when I try to add our Azure DevOps organization as Remote account I am getting following 'Authentication failed Object reference not set to an instance of an object'error . I have used Username and PAT which has needed scope and access. Appreciate any help on how to resolve this??? Following are the steps I performed after creating PAT in Azure DevOps with FULL ACCESS by following instructions in this URL https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops

Click on Remote Tab -> Add an account

Enter or select following values

Hosting Service: Azure DevOps

Host URL: https://organizationname.visualstudio.com/

Preferred Protocol: HTTPS

Authentication: Personal Access Token

Then clicked on 'Refresh Personal Access Token' button

Sourcetree Devops Pat Authentication Failed

Entered username and PAT as password

Which returned following Authentication failed error

Sourcetree Azure Devops Git

Pull

Authentication Failed For Azure Devops

Please help in resolving this issue.

Attachments

  1. STEP1.png
    46 kB
  2. STEP2.png
    49 kB
  3. STEP3.png
    25 kB
  4. STEP4.png
    58 kB

Sourcetree Azure Devops Url

Votes:
2Vote for this issue
Watchers:
3Start watching this issue