Azure DevOps compatibility issues

[stefanprodan]

In source-controller we use go-git to perform Git operations.

According to these issues go-git/go-git#64, src-d/go-git#335, src-d/go-git#1058 Azure DevOps doesn't implement Git v1 protocol and go-git doesn't implement v2 that supposed to work with Azure. As shelling out to the git binary is not an option for us, we have to figure out a way to Azure DevOps.

[artbegolli]

Watching this - curious as to what solution you guys come up with

[dirien]

Leaving a comment here too. As we are also affected by this.

@stefanprodan : Would it mean, in worst case we need to extend the go-git code for v2 handling?

[stefanprodan]

Would it mean, in worst case we need to extend the go-git code for v2 handling?

Either Azure DevOps implements Git v1 or we need to add support for v2 in go-git.

[vtbassmatt]

👋 hi, I'm the product manager for Azure Repos server (which is where protocol stuff lives). I'm afraid we have no plans to relax the requirement that clients support multi_ack. It looked from some of the related issues like go-git is not planning to implement multi_ack but is working on a v2 protocol implementation.

[phillebaba]

If anyone is interested following along the work to get this fixed. go-git/go-git#200

[stefanprodan]

With @vtbassmatt stance and @phillebaba PR getting rejected we are now investigating if it's possible to replace go-git with Go bindings for libgit2. Meanwhile if your are an Azure DevOps user, please consider switching to GitHub.

[dirien]

@stefanprodan That would be awsome!