What happens with the repository's old remote url when moving a repository to another project?

[sverro2]

Within the repository settings, there is an option to move the repository to another project. (Repository Settings -> Move Repository -> Selecting another project -> clicking move).

After moving the project, local copies of this git repository still seem to be able to push , pull and even clone the project using the old clone URL.

For how long will this old remote URL still work? A day? "For ever"? Just as long as there is not another project created with the same  (old) clone url?

[David Drinnan]

I came here wondering the same. Since the feature doesn't seem to be explicit, I would guess the old remote URL redirects are kept as best effort, but not guaranteed for any length of time. Probably to help smooth over the transition from the old repo name to the new, but nothing more.

It's been a few years. How did the old clone URLs hold up for yours?

[Thomas Johnson]

Just ran into this behavior for a repo that I moved and then recopied, so it still exists in the latest versions of Bitbucket Data Center.

Found this answer from Atlassian in another post or those who might be wondering what's going on: https://community.atlassian.com/t5/Bitbucket-questions/Bitbucket-old-ssh-URL-doesnt-change-after-renaming-the/qaq-p/1124814

If you'd like the behavior to stop, after moving your initial repo you can just add an empty repo of the same name and then delete it.