I haven't had a chance yet to get set up to capture logs - may later tonight if I'm lucky. I did a quick test invoking those rndlle32 invocations at the command line on Windows 10 and they both took me to the Azure DevOps Authorization page at https://www.syntevo.com/smartgit/azuredevops-callback. Invoking https://app.vssps.visualstudio.com/_apis/accounts in my browser returns a JSON list of Azure DevOps orgs that match my current login. I see the Azure logo in the branches view for a repo in one of the orgs I was able to configure in the Hosting Providers dialog.

Unfortunately I'm swamped with work right now and won't have time to do the more extensive testing that Marc suggested until this weekend, and only then if the fates smile on me. However, I was able to spend a little time fooling around with it today...

I had zero luck setting up Azure DevOps as a hosting provider using Personal Access tokens, but clicking the Generate Token button and then using the token generated at https://www.syntevo.com/smartgit/azuredevops-callback/ worked! I was able to create two separate Azure DevOps hosting provider accounts for two Azure DevOps orgs that I authenticate with using the account that I'm currently logged into my Windows workstation with. I was even able to give the Accounts more descriptive names in the SmartGit interface (one note: these accounts disappeared when I closed and then re-opened the Preferences dialog. I recreated the accounts and was unable to reproduce their disappearing act after that).

The SmartGit App Authorizations show up in the User Settings section of Azure DevOps. However, when I tried to generate a token for a third Azure DevOps org where I'm an administrator via a Microsoft account that is NOT the one I'm logged into my workstation with, SmartGit returned a 401 Forbidden error.

I installed the latest build and experienced the same issues as reported by hrant (although SmartGit never froze up on me).

In Azure DevOps, an Organization is the overall container for a collection of projects. Each project contains agile/scrum/kanban boards, pipelines, repositories, artifacts and more. Users are given access to an organization and personal access tokens are assigned to a user at the organization level. Azure DevOps admins then assign users specific permissions within the org. Any Microsoft personal, work or school account or a GitHub account can be used to create a user at the Org level in Azure DevOps. One or more Azure DevOps organizations can be connected to an Azure Active Directory. Hope that helps...

BTW - the text of this error message could use some tweaking...

Thanks Marc. I've installed the preview but I don't see Azure DevOps in the hosting provider list. Also, the hosting providers are listed in a different order than in your screenshot. I've also included a screenshot of my OS specs.

Thanks.

@Marc - I downloaded v 21.1 preview 4 and took a look at changelog.txt. I couldn't find any mention of Azure DevOps in the file - searches for "azure" or "devops" returned zero results....

Awesome!. Thanks Marc! I'll  play around with this over the weekend. 

After some reflection I realized that I actually haven’t had authentication problems with SmartGit and Azure DevOps for quite a while, so I spent some time experimenting to figure out just how SmartGit is authenticating to my repos in Azure DevOps. I ultimately determined that it uses Personal Access Tokens via the Git Credential Manager. So explicit support of PATs by SmartGit probably isn’t a critical feature after all. When you install Git (on Windows at least), you have the option to install the Git Credential Manager as well. As long as you do that you should have smooth sailing.

As far as advanced features like pull request integration goes, I don't mind managing pull requests in Azure DevOps, but SmartGit integration would be nice. It's worth nothing that neither Visual Studio nor Visual Studio Code currently provide support for Azure DevOps pull requests. As far as I can tell, there’s one extension in beta that was written by somebody as a pastime, and Microsoft had previously provided extensions for functionality in VS and VS Code that supported pull requests but they’ve been or are being deprecated and have not yet been replaced. So Pull Request integration could be an opportunity for SmartGit.

Azure DevOps isn’t as popular as GitHub and maybe not even as popular as GitLab, but a lot of people do use it, so adding Azure DevOps support could help increase the SmartGit user base. I generally prefer using SmartGit over Visual Studio or VS Code for repository management.

The main feature I'd like to see to see for the initial integration of Azure DevOps and SmartGit is to be able to authenticate to an Azure DevOps repo from within SmartGit using an Azure DevOps Personal Access Token.