To clarify, assume in good faith that pivot in context means compelled towards involuntary action---i.e. unexpected loss of local data, as opposed to a matter of routine shift in workflow---where the remote forge is being tapped for its secondary function as off-site backup.

The question was more intended to probe remote UX resilience near the limits of pain when faced with massive git repos which primarily capture binary assets/artifacts.