sandbox-adopt

To move files from an individual sandbox to a shared team directory, you can automate the relocation of specific items while simultaneously cleaning up related symlinks. This ensures the shared workspace receives the updated files safely for team collaboration.

Cleaning up symlinks is necessary when sharing sandbox files to prevent broken links across the development environment. Removing all symlinks to the relocated item ensures that team members access the correct shared version instead of dead local references.

The best way to stage shared sandbox files in version control is to automate the migration process to handle relocation and symlink cleanup simultaneously. This safely stages the shared file in version control during the transfer to the team workspace.

Yes, you can use this sandbox migration approach for experimental feature branches. It is specifically designed for collaborative development environments where engineers need to seamlessly adopt and share experimental or project files into the team folder.

After a sandbox file is adopted into shared storage, all existing local symlinks pointing to that item are automatically removed. This symlink cleanup prevents broken paths and ensures the shared file is updated safely without leaving dead links behind.