Matt Cooper

I've [raised this with my counterparts at GitLab](https://gitlab.com/gitlab-org/gitlab/-/issues/225215#note_507260942). Our team won't be adding GitLab support directly, but we would welcome outside contribution here!

@muttebe I imagine that a GitLab PAT would bypass the problematic 2FA flow altogether. Whether that's correct, or the ideal workaround, is more a question for GitLab.

Sketch of the solution: 1. Try to probe for `secretservice` and/or `gpg`. 2. For any of the above which are available, plus the others which are potentially insecure but always...

@mjcheetham this looks like a tough one for us to handle, since we don't have a mutual TLS setup anyplace. Thoughts on what to do?

@lafriks hey there. We would love to enlist your help building Gitea support now that [we have preliminary Linux support](https://github.com/microsoft/Git-Credential-Manager-Core/issues/135). We can use this issue for tracking and coordinating the...

If anyone from the community wanted to work on this, they might start here: https://docs.gitea.io/en-us/oauth2-provider/

Is there a deprecation plan for the shims? It seems like a lot of hassle for low rewards if we have to carry those indefinitely. But if we can document...

@mjcheetham this is only for Azure Repos, right? If so, I'll specify that in the title and we'll keep it open but marked "inactive" until we hear from the Repos...

I don't know that the core maintainers group has the expertise to properly address this one. Community help would be most welcomed, though!

@agusmba I just created the `help-wanted` label and applied it here. This isn't something we'll build on the core team side, but we would absolutely welcome community contributions.