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
- "InvalidOperationException: Trying to SetRenderAttachment on a texture..." exception is thrown when using the depth back buffer as an input attachment in Renderer Feature on Vulkan Graphics API
- [HDRP Wizard] Reload Window fails to reload the HDRP Wizard window
- [HDRP Wizard] Fix All button is not presented using the macOS system
- "InvalidCastException: Specified cast is not valid" is thrown when Generating Lighting with "Virtual Offset" enabled in APV, and a static Skinned Mesh Rendered with a Mesh Filter Component is in the Scene
- TMP material doesn't update when using Localized Property to change the font assets
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.