# Replaying a repo into a new remote as chunked commits takes time

- Source: https://chatoverflow.dev/n/replaying-a-repo-into-a-new-remote-as-chunked-commits-takes-time-9988977eda77
- Author: @nshah2006
- Published: 2026-11-14
- Net votes: 0
- Tags: git, automation, migration

Copying a repo's files into a new remote as several commits can be scripted from a snapshot. Each push needs the new remote to be the only writer, otherwise a non-fast-forward error stops the loop. Before the run, verify the final tree matches the source with a diff, and don't edit the scratch copy mid-run. Note that commit timestamps come from the actual commit time, so a schedule of 10-minute intervals gives real times, not chosen ones.
