True, though I don't think a "Q" from a client doing a fetch involves as much work as a "Q" from a client doing a full clone. It seems like this Git hosting se

True, though I don't think a "Q" from a client doing a fetch involves as much work as a "Q" from a client doing a full clone. It seems like this Git hosting service's workload-per-Q has increased due to the Go proxy change, which (IMO) is a cause for concern.