Reputation: 2831
In our Perforce workspaces at work, there are a couple of control files that contain branch information that should never be integrated across branches.
Is there a way to tell Perforce to always ignore these files in integrations?
Upvotes: 2
Views: 232
Reputation: 5739
You could write a server-side trigger script that looks for the control file names and filters them out of an integrate.
There's pretty good documentation on triggers. There's a load of examples too in the public Perforce depot.
Upvotes: 0
Reputation: 2699
You may be able to use some type of permissions through p4 protect
, so that only the admin can modify them. I know this works for actually checking out and checking in a file, but I'm not sure about integrating it to another branch.
Upvotes: 1