Your comments
Azure Refreshing shouldn't block the GUI and repository refreshing for 30 seconds sounds excessive. Please send periodical thread dumps to smartgit@syntevo.com:
https://www.syntevo.com/doc/display/SG/Periodical+Thread+Dumps
Build 17083 now supports this optimized URLs, for "visualstudio.com" as well as "dev.azure.com" domains. On the other hand, I have added another check to ensure that the remote URL ends with the repository name and does not contain additional, unexpected path segments. Hopefully that doesn't break URLs which have already been working now :)
Conflict resolution has been reworked in 21.1. Also, you may want to enable/disable "Swap ours and theirs ..." option in the Preferences, Conflict Solvers.
Is this still an issue with 21.1 preview latest build (Help|Check for Latest Build)?
> 1- The only way I could make Smartgit reflect the changes done on the Web is by toggling / un-toggling , not sure if that is by design
Clicking the Azure toolbar button should refresh all information. Refreshing the Log view should also refresh all information. After any Azure-related operation information should automatically be refreshed.
> 2- Actions on Comments are missing, but I'm sure you know about that
In the Window|Comments view there should be Edit, Reply, Delete. In the Changes view, if a pull request node is selected in the Log, it should also be possible to add new comments.
> 3- If I make a code inline comment in SmartGit, it is not reflected on the Web, the reverse works, but I need to do the toggle dance to see the changes.
I can't reproduce that. I guess it will be time for a shared test repository. Will it be possible for you to set this up?
Approve definitely makes sense. There are similar topics for GitHub and Bitbucket, too. As always, we will probably not support every possible option but try to find some common GUI which will work for all Hosting Providers. I guess that would be Approve vs. Reject with an optional comment. How important is the auto-complete functionality?
Please post a new UserEcho topic for "Azure DevOps: Approve Pull Requests" and include information on must-have and nice-to-have options.
OK. This sounds like a very specific task designed for your environment. I'm still not sure that the client-side is the appropriate place for it because you have to ensure that everyone is using a client which performs these additional tasks. Azure Webhooks don't seem to be useful here, but Pipelines might be. Also, there already seem to be some existing integrations between Azure and JIRA already [1].
Even on the client side, this can be implemented outside of SmartGit, e.g. by Git client-side hooks. Hence, I don't think we would address this issue in SmartGit.
[1] https://devblogs.microsoft.com/devops/azure-pipelines-integration-with-jira-software/
I can confirm that the URL of your origin is not yet supported: it's missing the "project" part. My visualstudio.com URLs look like: https://org.visualstudio.com/project/_git/repo
Now I'm wondering why this "project" part is missing for you? It seems that I can only create repositories within a project...
Customer support service by UserEcho
Thanks for your feedback! You are right. SmartGit wasn't actually prepared for on-premise instances. I have now uploaded build 17090 which should work better: Help|Check for Latest Build
I was able to confirm that the REST API works for my test setup (VM). I wasn't able to access repositories using Git from outside of the VM: I'm always ending up with "Authentication failed for ...", no matter which username/PAT combinations I'm using. How do you access your Git repositories from command line?
Another note: for every REST call, the "api-version=" is included, which currently defaults to "6.0". This seems to work with the most recent Azure DevOps Server. If you encounter error messages related to the API version, you can change this in the Preferences, Low-Level Properties, "azure.apiVersion".