How to maintain physical branch folders for git as available in TFS? -

We have a great product and has many features, each feature would take too long, so we have a while TFS maintains branches with facilities For example,

  MAIN / PROJECTMGT EMAILMGT etc ..   
 and once completed, they have been merged back into MAIN, and Each separate development team works on different branches.    
   
   
   
  Clear view of files in different folders Since we need to check and review the branch before merging, we must also look at the struggles of different branches and they have to be resolved clearly.  
 Now we are moving on git, and as I am learning GIT, I am finding it difficult to organize branches, while working on file and folder structure, we do not know that We are in exactly what branch.  
 We have just run a test on GIT, and most of us who work on many branches have become confused and we  
 I was reading about this And I suggested to create several clones to emulate the TFS type physical folder's branches.  
 Can someone guide me how can I do this? I am using Visual Studio Tools for GET.  
  UPDATE   
 Based on the comments, here are our current difficulties.           Like the Nugget package, we have other third parties. There are different versions of the library (Binaries) and different branches.  
 
 At the time of merge, its disturbance, we keep asking ourselves which branch we are in, though VS. This is easy because the physical folder path tells us our branch.   
 
 I have to remember that when we checked the branch three days ago we were, however, when you go to source code explorer, VS. The Geet Tools display it, but we have many V.S. Examples are also unable to open.   
 
 We are ever looking for workflows without using "switch branch" ever     
 
 
 Based on the comment on the question, it will create more than one clone There will be an answer (possibly check-out in different branches).  
   However, this is not the best solution for best solution  , for the following reasons:  
 
 
 each Additional clone uses additional drive space.   
 
 The use of additional clones is probably not the best way to make merge easier   
 
 Using additional clones to simplify the test Can not be the best way.    
 Step 1: Create a local clone  
 Since you mentioned that you are using buttocks, you do not already have a local clone If you happen to be, you have to do this step.  
  git clone & lt; Url-to-repo & gt;   
 This will clone your repo and automatically check the  master  branch, assuming that  master  branch is your default branch Set up on the butt.  
 Step 2: Create a clone for each branch you want  
 If you have additional branches for which you want a separate checkout, then you can repeat the following branches Clone another for each branch:  
  git clone & lt; First local-clone from path & gt; GIT Checkout & lt; Branch & gt;   
 Note that each clone will basically end at least using the same drive space. It may be possible to reduce the place used by using  - shared  or  - context  options for the  git clone , but I can not do this  
 documentation  
 
. Get enough information about