Disabling + S file in Perforce

Question

The Perforce filetype system includes + S, modified to indicate that the file is a temporary file. The consequence of this is that the file history is not saved for this file - only the latest version is supported and is replaced by each new check.

This is obviously a dangerous flag to accidentally establish what we recently discovered. Is there any way to ensure that this will not be used in the future?

Answer 1

You can write a pre-commit trigger that looks at the list of files for this flag, rejecting the commit, if so.

See this chapter of the Perforce manual for more information .