| title | Use TFVC and Git repos in the same project |
|---|---|
| titleSuffix | Azure Repos |
| description | Using Version Control for your project in Azure DevOps |
| ms.assetid | F1DE1F34-50BD-49A6-BF67-D27F884944F4 |
| ms.subservice | azure-devops-repos-git |
| ms.service | azure-devops-repos |
| ms.custom | archive-candidate |
| ms.topic | overview |
| monikerRange | <= azure-devops |
| ms.date | 09/10/2018 |
[!INCLUDE version-lt-eq-azure-devops]
In Team Foundation Server 2015 Update 1, a project administrator can add a Git repo to a project created with Team Foundation Version Control (TFVC). You can also add a TFVC repo to a project created with Git. This allows you to adopt a new version control system while preserving all the data in your project.
[!INCLUDE azure-repos-prerequisites]
Because permissions are applied at project creation time by a process template, there will be a small amount of work to correct permissions for a new repo type.
The project administrator will need to apply some project folder-level permissions when the project folder is created. Go to the Version Control administration page and select the "$/ProjectName" node in the tree. To set up the same groups as any of our default process templates (Agile, Scrum, CMMI), add the following TFS groups and permissions:
- [ProjectName]\Readers
- Allow: Read
- Not set: All others
- [ProjectName]\Contributors
- Allow: Check in, Check out, Label, Lock, Merge, Read
- Not set: All others
- [ProjectName]\Build Administrators
- Allow: Check in, Check out, Label, Lock, Merge, Read
- Not set: All others