Search Issue Tracker
Won't Fix
Votes
0
Found in
Issue ID
1185134
Regression
No
[VCS] Option to do RevertUnchanged on each Submit ("revertunchanged" in p4)
In many cases files are checked out without actual changes to them happening.
Perforce and P4V default to "submitunchanged", i.e. everything is submitted, no matter whether changes happened or not.
Maybe we should default to "revertunchanged", or at least have an option for that somewhere.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2020.1.X):
In my opinion this should be rejected as workspace setting verification is something that you can configure Perforce server to do (if you can find the examples in the wild west of the Perforce docs). On balance I think it's safer to implement this there than either rolling our own workspace settings verification or writing our own revert unchanged on check-in, as there are lots of ways in which we could break expected Perforce behaviours.