I transferred ownership of a personal repository from one workspace to another. Under those circumstances, am I right that push/pull with the old address should still work transparently (i.e. it should redirect to the new one)? I have admin rights over the new repository/workspace, as well as being owner of the old workspace. From these old posts:
https://community.atlassian.com/forums/Bitbucket-questions/Bitbucket-old-ssh-URL-doesnt-change-after-renaming-the/qaq-p/1124814
https://community.atlassian.com/forums/Bitbucket-questions/What-happens-with-the-repository-s-old-remote-url-when-moving-a/qaq-p/1109070
I had expected that this redirect would work, but it is not working. If I push/pull to the old repository from the command line I get this error:
remote: You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated.
Is there something I need to do differently to activate this redirect feature? It would save a lot of hassle if that redirect was possible. The project was a submodule in a parent project, and I can’t see any way that past commits from the parent project can be matched up with the correct submodule commit (via ‘git submodule update’) unless the original workspace link still works transparently as a redirect (as I had been anticipating that it would). Can anyone advise? Thanks.
