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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
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.