Changes in git repo url of target clones new repo

[ar13pit]

@MatthijsBurgh @Timple Is cloning the repo again the desired behavior? Or should we just be moving the repo directory to the new location, as the current behavior leaves the older copy in place for the user to manually remove it

[MatthijsBurgh]

I think this indeed undesired.

People could have local changes etc. If these are just gone, that is wrong.

[Timple]

The new URL might be vastly different. So you 'cant' simply move it then...

[MatthijsBurgh]

@Timple we don't need to cover all cases, just the most common ones. I think the most common ones are repos being forked or going back from fork to original repo.

Do you have other cases in mind?

[Timple]

I don't have a strong opinion about this by the way, so I'm good with all outcomes.

You can also simply give a warning in case of local changes and don't touch it.

[ar13pit]

One case that I encountered is renaming of the repo in the URL

[MatthijsBurgh]

Both in my case and the case of @ar13pit we moving the repo is a safe option