Issue Accessing Repositories After Rename Attempt

Unity Services
,
1

Hello,

I encountered an issue with my repositories (on @cloud) after trying to rename one of them.
Here’s the situation:

I initially had the following repository structure:

MyRepoRoot
MyRepoRoot/Child-1
MyRepoRoot/Child-2

I attempted to rename MyRepoRoot to MyRepoRoot/Child-3, but the system raised the error:
“Module can’t be created because parent repository doesn’t exist”

After this error, all three repositories (MyRepoRoot, MyRepoRoot/Child-1, and MyRepoRoot/Child-2) became inaccessible. Unfortunately, I had to recreate them from scratch, resulting in the loss of the entire history.

I’ve attached screenshots that illustrate the issue:

Clipboard Image-1
Clipboard Image-1845×233 15.4 KB

Clipboard Image-2
Clipboard Image-2896×484 33.7 KB

Clipboard Image-3
Clipboard Image-3865×361 19.7 KB

While I’ve resolved the situation for now, I wanted to report this issue as it caused unexpected data loss and disruption. I would appreciate it if you could investigate and ensure others don’t face similar problems.

Thank you for your time and support!

Best regards,
Giovanni

2

Hi Giovanni,

First of all, thank you for reporting it.
Can you share how did you recover it?
Were the three repositories populated?

Best,
Héber.

3

Hi Héber,

Unfortunately, I was unable to recover the original repositories. I had to recreate them and repopulate them using the latest version of my sources from my local workspaces.

One important note: before linking the recreated repositories to the local workspaces, make sure to delete the .plastic folder in the workspace directory. Failing to do so can result in all files in the workspace being deleted, as happened to me. I had to recover my files from an older backup.

I hope this information helps to avoid similar issues for others in the future.

Best regards,
Giovanni