Unity Issue Tracker - Local package files and Project Settings are automatically marked for add after VCS is reconnected/refreshed
Closed
UUM-17928
Local package files and Project Settings are automatically marked for add after VCS is reconnected/refreshed
Unity: Version Control
VCS
Won't Fix
6.5.X
6.4.X
6.3.X
6.2.X
6.1.X
6.0.X
2023.2.X
2022.3.X
2021.3.X
2020.1.X
2019.3.X
Cancelling: the 6000.1 version has reached its end of life. If you need additional fixes, please upgrade to a newer Unity version.
Cancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.
How to reproduce:
1. Create a new project in your prefered workspace and open it
2. Connect it to Perforce
3. Add a local package (Drag a separate package to the "packages" folder)
4. Observe that its files are all automatically marked as add (This is expected since this is a local package)
5. Revert some of the files and refresh the VCS Window (Thre reverted files should be marked as "local" instead of marked for add)
6. Observe their status again
Expected result: the status remains "local" (the red dot icon)
Actual result: the status reverts back to "added local" (the plus sign)
Reproducible in: 2020.1.0a1, 2019.3.0b1
Not reproducible in: 2019.2.3f1, 2018.4.7f1
Note: This also means that the local package files or project settings cannot be reverted in the VCS Window, they will be re-added upon reconnect/refresh
Prioritise and Follow this issue
Have a workaround or additional info about this issue?