After a Move/Rename operation, the old asset file is replaced by a "redirector" file of the same name, pointing to the new asset file.
A problem arises if this redirector is not committed immediately with the new asset:
the old asset is still in source control
the redirector is not in source control
the new asset is also in source control
there are two identical files checked in the source control system. Thus the operation appears as a copy/duplicate, instead of a rename.
This happens when the new file is directly selected for check-in: only the new file is proposed for check-in (not the redirector itself).
=> Users must select a whole directory or game project to commit all files with an atomic multi-file check-in.
After a Move/Rename operation, the old asset file is replaced by a "redirector" file of the same name, pointing to the new asset file.
A problem arises if this redirector is not committed immediately with the new asset:
This happens when the new file is directly selected for check-in: only the new file is proposed for check-in (not the redirector itself).
=> Users must select a whole directory or game project to commit all files with an atomic multi-file check-in.