Couple of Git repositories created in our workspace are no longer visible, which had been actively used by members of the workspace till recently. Looking at the audit trail shows that there has been no activity related to deletion or modification of these repositories. They have simply disappeared from our workspace.
Trying to access the old URL for the repositories just shows a Repository not found, 404 page. Trying to pull from remote displays the error:
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.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Permissions should not be an issue since using an account admin privilege for that workspace also shows the same issue. Has anyone else faced such an issue of disappearing repositories? Any advice would be very appreciated.
Hello @indrajit_ghosh and welcome to the community!
I confirmed the email of your community account has access to more than one workspace. It might be the case you are looking at the wrong workspace. To confirm this you can log in on Bitbucket, click on your personal avatar in the top right corner, and select All workspaces. You can then click on each of the workspaces and check if the repository in question is present in any of them.
If you are still not able to find the repo, could you share with us the masked name of the workspace and repository that is missing?
For example, the masked version of workspace my_workspace and repository my_repository would be m*_*******e/m*_*********y
This is so we can check for that repository in our internal tools.
Thank you, @indrajit_ghosh !
Patrik S
Hello @Patrik S, thanks for the prompt response. We finally figured out what happened. One of the contributors in the workspace was trying to reorganise the repositories and, in the process, moved them to a newly created workspace. It was really a (lack of) communication issue!
I think this can be a good use case for the audit logging system for Bitbucket to log an event if a repository gets moved to a different workspace.
Thanks again.
Regards,
Indrajit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @indrajit_ghosh ,
Glad to know you have figured out where the repos were.
As for logs related to repo transfers to be included in the Workspace Audit Logs, we do have an open feature request for that :
I would encourage you to add your Vote there, and also mark yourself as a Watcher to receive first-hand updates whenever there's progress on the implementation of that feature.
Thank you, @indrajit_ghosh !
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.