Preventing check-ins on branched folder

[jsiegmund]

Hi,

We've recently started using the branching feature of Fortress and are very pleased with it. Now I came across a developer who checked in code directly into the main branch. Offcourse I don't want my developers checking in code directly, they should use the appropriate development branch and that's merged with the main branch after testing is done. Is there a way to prohibit check-ins on branched folders? Maybe I could use permissions or something like that, but that always requires some action to get it right. I would like source control to automatically block those main branches and only allow merging of branches with changes in them.

[Beth]

You would have to dis-allow access to the trunk for that developer to prevent changes being checked into it.

Another option would be to pin the trunk, and that will block check-ins, but the developer can then remove the pin, check in, then put it back, so it would take trusting the developer not to circumvent it.