If they started with support Git Remotes and then supporting specific platforms, they would have covered all use cases from the get-go, albeit with slightly poorer UX.
But instead they chose to only support specific platforms, missing plenty of people who actually want to use this, but can't.
I bet GitHub covers the vast majority of their target users.
[0]: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protoco...
> I bet GitHub covers the vast majority of their target users.
Sure, but if they added Git, they would reach everyone using GitHub + everyone else who is using Git.
With powerful primitives you can build powerful abstractions, Git is one of the examples of this. But if you instead focus on a single-use case (using GitHub), adding the rest becomes a lot harder, than if you started with the basics. Something 90% of product people in SF seems to have forgotten lately (or never learned?)
> You can deploy the source code directly from your GitHub repositories (support for GitLab and Bitbucket is coming soon).
Naming specific git hosts suggests it may not be available on "arbitrary Git repositiories" in the near future, but looks like they are at least planning to broaden the options for where to have your code live