> If I try to Generate Token instead, I get redirected to a browser and get an Authorization Code? however this is not clear as to what organization it is using? I guess we should rename it to "Organization". It's the same what will be used as prefix for your URLs. > What does the Account field represent? is it a label to name the account or is it actually my account email? Or is it the organization name? I generally prefer using SmartGit over Visual Studio or VS Code for repository management.
So Pull Request integration could be an opportunity for SmartGit.Īzure 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. 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. It's worth nothing that neither Visual Studio nor Visual Studio Code currently provide support for Azure DevOps pull requests. As long as you do that you should have smooth sailing.Īs 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.
#SMARTGIT COULD NOT CONNECT TO THE REPOSITORY INSTALL#
When you install Git (on Windows at least), you have the option to install the Git Credential Manager as well.
So explicit support of PATs by SmartGit probably isn’t a critical feature after all. I ultimately determined that it uses Personal Access Tokens via the Git Credential Manager. 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.
0 kommentar(er)
