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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
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.