Yes, exactly. Git worktrees will for instance make it easier to merge changes between multiple checked out branches without pushing upstream.

For big repositories with long histories (like Qt), worktrees also save some disk space.

Moving work/commits from one local clone to another is something I do regularly - just using vanilla git push/fetch.

I’ll grant that saving disk space is a concern for many - not for me - the largest repo I use is 2-3 million LOC with about 10 or 15 years history and the 4-5GB per clone doesn’t bother me.

> just using vanilla git push/fetch

Right but that's quite a lot more faff than not having to do anything at all.