After repo renaming it works via both ssh links

[timofey_shklyarov]

In Stash I renamed a repo. Now it works via git ssh via both url-s: old and new. And has been working  for a couple of days already. And new commits are seen. Stash restart needed? Is this a feature ?..

• Atlassian Bitbucket v5.6.2

[Ana Retamal · Accepted solution]

Hi Timofey,

When a repository is renamed the URL is updated immediately and a redirect is implemented immediately. New and old browser and clone URLs will both work.

This was already reported in our portal, if you're interested you can join the discussion at BSERV-11048.

I've been checking with our team and there is currently no option to disable that feature. However, there is a workaround that could be applied to stop this behaviour from happening. The steps would be as simple as:

1. Create a new temporary repository (with the same name as the old one) in the same project
2. Delete the new temporary repository.

Notes: This only applies to the repositories that have been already moved and the behaviour will keep happening on the repositories that will be moved in the future. This means that if repositories will need to be moved/renamed, this operation will still need to be done. Keep in mind that removing the data directly from the database is not supported and should not be performed for this scenario.

Hope that helps!

Ana

[Sonja Athing]

Hello Ana,

I added the tag 'Fisheye-Crucible' to this post because your insight was really helpful as per managing Fisheye repos and a Crucible project.

Instead of just renaming the Fisheye repo to the new name (which Fisheye would allow me to do),  I instead added the newly named (was renamed inside of Bitbucket)  repo to Fisheye and then included it into the Crucible project needing the repo.  Finally,  removed from the Crucible project the old name repo.

Thank you!

-Sonja