> 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...

Are you doing this on the client-side? To me this sounds more like a server-side task which would be triggered by some post-receive hook. Are all three steps done at the same time? If so, when exactly?

The notification was not yet triggered for "visualstudio.com" domains. This is fixed now in build 17079.

> repos where the origin URL is specified as https://[org].visualstudio.com don't show the Azure logo in SmartGit.

That's unexpected. Such URLs should work since build 17074 and "DefaultCollection" should be handled correctly since build 17078. @hrant has confirmed this -- please see our discussion above. Are you referring to exactly this kind of URLs or am I misunderstanding?

Thanks! Build 17078 should now correctly handle "DefaultCollection".

Thanks, I understand now. Paging ($top,$skip) isn't supported for that API. I have uploaded build 17075 which should fix this problem. This most likely also explains the out-of-memory error: SmartGit reads and caches an infinite amount of JSON objects and finally runs out-of-memory.

@hrant and @Martillo, again thanks for your testing and feedback. I have now uploaded build 17074 which comes with following changes/fixes:

• Pull Request: Open in Web Browser
• Fix Commit view Open link
• Support for .visualstudio.com URLs (hopefully)
• Fix possible internal error related to comment IDs
• Retract/Reject Pull Request is now both "Abandon Pull Request"; in all cases, for all Hosting Providers both functions are about "cancelling" a pull request, not about reviewing where one would Approve/Reject a pull request