Warn on Git fetch from secondary if the secondary is lagging the primary
Replication delays exist when using Geo, and depending on the situation could be up to a few minutes. This delay could be problematic if CI builds use the secondary because the commits may not yet be available. If we know that there are pending changes that haven't been replicated, we should help the consumer know they are getting stale data.
Proposal
When fetching from a geo secondary, check if there are pending tasks in the queue for that repository, and show a warning that the secondary is out of date and that they should fetch from the primary.
Links
Edited by James Ramsay (ex-GitLab)