Question

We are allowing external consultants to work on a portion of our source. We created a new TFS project and granted them rights to that. Branching does work between TFS projects, so we can branch the “real” TFS project they’re working on to the consultant project. However, we only want to expose portions of it. Here’s what we want (simplified):

OurProject
  Mainline
    Applications
      Secret1
      NewApp
    Libraries
      Secret2
      Shared

ConsultantProject
  Mainline-Branch
    Applications
      NewApp
    Libraries
      Shared

If we simply branch Mainline and delete the Secret folders on the branch, merging back must be done carefully to avoid deleting the Mainline Secret folders. We want to simplify future merges (both ways) while minimizing risk.

How can this be accomplished?

Answer 1

I know this may not be answering your question, but rather the intent of your question. Why not just set permissions to hide those secret items from the consultants and branch as you would any other time?