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
  
  

When exactly did this happen?

For my small test organization the paging logic works. Is it possible that your organization has really many repositories and SmartGit is not actually stuck but it only takes a long time to complete? When comparing:

https://dev.azure.com/org1/_apis/git/repositories?api-version=6.1-preview.1&$top=50&$skip=0

and:

https://dev.azure.com/org2/_apis/git/repositories?api-version=6.1-preview.1&$top=50&$skip=50

in your browser, are results different?