Here, we will focus on eliminating any git configuration differences needed for users of GitLab Geo. The desired state is that, independent of the location of a user, the git configuration is the same. This would eliminate the need for systems administrators to maintain different configurations in different geo locations. When using git directly, a user would not need to know about Geo because all requests are proxied to the `primary`. This will likely result in a single URL for all git operations e.g. `https://git.example.com`. There won't be a distinction between `primary` and `secondary` git URLs. This would be a direct continuation of supporting multiple Geo `secondaries` behind a load balancer. The technical solutions to achieve this could be, for example, either a global load balancer or a geo-based DNS service.