Hey all, I’m a long time version control user but as we onboard more people onto the team who are less familiar with the process there’s one weird quirk I’m struggling with:
We are trying to get people to work in isolated scenes so two people checking in their work won’t have conflicts. However I’ve often found that even if you don’t make changes to a scene, Plastic SCM will report that scene as having changes. When I’ve looked at the actual differences, it’s usually something like a fileID changing, or a position changing by some fraction of a cm that I assume happens from some automatic calculation.
My instinct is to tell people to ignore these changes, and if a scene or file that they didn’t touch is reporting changes just undo them before checking in. However I also know I like to review these types of files before reverting them in case I did accidentally change them – for example accidentally adding something to Scene A instead of Scene B. My concern is that by undoing changes, someone can lose work they already did and not even realize it until much later.
The alternative is to tell people to check in everything just in case, but then you risk checking in some random experiment you did – for example toggling off objects when testing how something works and forgetting to toggle them back on. This runs the same risk of someone accidentally overwriting someone else’s work without realizing it.
So I’m wondering if there’s any way to parse out minor changes – things like updated fileIDs, changes to position/rotation below a certain threshold, etc.? Or a way to prevent Unity from making these automated changes? Or do you have any guidelines you share when onboarding new people to ensure their changes are included without accidentally overwriting other people?