Answers: <p>If you have alread added one repository to your project then you should do the following:</p>
  <ol>
  <li>On left hand side panel click on <code>repos</code></li>
  <li>On the top panel you will see <code>organization-name</code>/<code>project name</code>/<code>Repos</code>/<code>Files</code>/<code>current repository</code> - click on <code>current repository</code> which has a git icon next to it and a down-arrow to its right</li>
  <li>Press on <code>Import repository</code></li>
  <li>Enter the details of your repository on the pop-up pannel</li>
  </ol>
  
Answers: CC BY-SA 4.0
Answers: 2021-07-18T09:06:50.427Z
Answers: 2021-07-18T09:06:50.427Z
Answers: Trake Vital
Answers: <p>As an alternative to DrGriff's answer..</p>
  <ul>
  <li>Go to the [Project Settings] for your project and select [Repos] / [Repositories] on the left-hand side</li>
  <li>There should be a &quot;Create&quot; button on the top right (below your profile button)</li>
  </ul>
  <p>If you don't see the &quot;Create&quot; button your user almost certainly does not have the permission to create repositories for this project.</p>
  <p>Looking at <em>ataraxia's</em> comment, I had the same issue. I was both a project and collection administrator but could not create a new repository. The reason being that I had explicitly set &quot;Deny&quot; on the &quot;Create repository&quot; permission for &quot;Contributors&quot;. An explicit Deny on one of the groups you belong to seems to override your Allow privileges. So please go over your group member privileges, perhaps that solves your problem?</p>
  
Answers: CC BY-SA 4.0
Answers: 2023-02-15T15:07:04.187Z
Answers: In my case, this was the issue. As I was still new to Azure DevOps, I just assumed that since I was an admin of the project that gave me rights for everything. Turns out, looking at Nolte's answer, there was some more setup I had to do but never did: under Project Settings->General->Permissions I realized that I hadn't touched the settings for ANY of groups listed and most of them had their values set to "Not Set". Nolte's solution not only fixed the OP's issue (and mine) but made me realize that there were still more permissions to be set up in general.
Answers: RhomburVernius
Answers: CC BY-SA 4.0
Answers: 2020-11-18T09:08:16.460Z
Answers: 2020-11-18T09:08:16.460Z
Answers: Nolte
Answers: <p>In your DevOps project:</p>
  <ul>
  <li>Project Settings</li>
  <li>Repos</li>
  <li>Repositories</li>
  <li>[ + Create ] (top,dx blue button)</li>
  </ul>
  
Answers: CC BY-SA 4.0
Answers: 2024-06-21T09:21:29.357Z
Answers: 2024-06-21T09:21:29.357Z
Answers: P.O.W.
Answers: <p>Following works for me:</p>
  
  <ul>
  <li>Click on your Project and then [Repos] in the left hand menu.</li>
  <li>Along the top, you'll see the bread-crumbs: <code>Organization / Project / Repos / Files / {NameOfCurrentRepo}</code></li>
  <li>Click the down arrow next to that and you'll see the option to add a <code>new Repository</code></li>
  </ul>
  
  <p>If that's not available, then it must be a permissions setting that I'm not aware of.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-02-24T17:14:02.170Z
Answers: This is the correct answer - it's a horrible interface, but thanks for the assist.
Answers: JohnFF
Answers: CC BY-SA 4.0
Answers: 2020-08-08T20:14:53.407Z
Answers: I cannot see this option and I should have ALL permissions. I'm the only user on the AAD, I created this project, (original) repo and everything involved with it. How can I not have permission to add a repo to it?!
Answers: ataraxia
Answers: CC BY-SA 4.0
Answers: 2022-09-20T16:05:38.627Z
Answers: As of late 2022 this still seems to be the correct answer. Not at all obvious.
Answers: KeithL
Answers: CC BY-SA 4.0
Answers: 2024-07-15T17:28:04.353Z
Answers: As of mid 2024, this still seems to be the correct answer. Come on Microsoft! Why did they have an ambiguous "Files" as the top level for all your projects repos?
Answers: ATL_DEV
Answers: CC BY-SA 4.0
Answers: 2020-02-24T07:35:05.283Z
Answers: 2020-02-24T07:35:05.283Z
Answers: DrGriff
Body: <p>My organisation uses Azure DevOps and we want to use git as our repo.</p>
  
  <p>But, Azure projects seem to only allow one git repo per project.</p>
  
  <p>This is bizarre to me! Projects and repos are usually separate. One project may involve development on several tools, and a tool may be used by several projects.</p>
  
  <p>How can I get projects to engage with multiple git repos?</p>
  
Tags: <azure>
Title: How to have multiple git repos in an Azure DevOps project?
UserDisplayName: JohnFF
ThreadText: # How to have multiple git repos in an Azure DevOps project?
  
  (Asked by: username_0 on 2020-02-23)
  
  My organisation uses Azure DevOps and we want to use git as our repo.
  
  But, Azure projects seem to only allow one git repo per project.
  
  This is bizarre to me! Projects and repos are usually separate. One project may involve development on several tools, and a tool may be used by several projects.
  
  How can I get projects to engage with multiple git repos?
  
  **Tags:** azure
  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_5 on 2020-02-24. Score: 33 | Accepted answer
  
  Following works for me:
  
  * Click on your Project and then [Repos] in the left hand menu.
  * Along the top, you'll see the bread-crumbs: `Organization / Project / Repos / Files / {NameOfCurrentRepo}`
  * Click the down arrow next to that and you'll see the option to add a `new Repository`
  
  If that's not available, then it must be a permissions setting that I'm not aware of.
  
  > **Comments:**
  > **username_0**: This is the correct answer - it's a horrible interface, but thanks for the assist.  
  > **username_6**: I cannot see this option and I should have ALL permissions. I'm the only user on the AAD, I created this project, (original) repo and everything involved with it. How can I not have permission to add a repo to it?!  
  > **username_7**: As of late 2022 this still seems to be the correct answer. Not at all obvious.  
  > **username_8**: As of mid 2024, this still seems to be the correct answer. Come on Microsoft! Why did they have an ambiguous "Files" as the top level for all your projects repos?  
  
  ---
  
  ### Answer by username_1 on 2021-07-18. Score: 3
  
  If you have alread added one repository to your project then you should do the following:
  
  1. On left hand side panel click on `repos`
  2. On the top panel you will see `organization-name`/`project name`/`Repos`/`Files`/`current repository` - click on `current repository` which has a git icon next to it and a down-arrow to its right
  3. Press on `Import repository`
  4. Enter the details of your repository on the pop-up pannel
  
  
  ---
  
  ### Answer by username_2 on 2020-11-18. Score: 2
  
  As an alternative to username_5's answer..
  
  * Go to the [Project Settings] for your project and select [Repos] / [Repositories] on the left-hand side
  * There should be a "Create" button on the top right (below your profile button)
  
  If you don't see the "Create" button your user almost certainly does not have the permission to create repositories for this project.
  
  Looking at *username_6's* comment, I had the same issue. I was both a project and collection administrator but could not create a new repository. The reason being that I had explicitly set "Deny" on the "Create repository" permission for "Contributors". An explicit Deny on one of the groups you belong to seems to override your Allow privileges. So please go over your group member privileges, perhaps that solves your problem?
  
  > **Comments:**
  > **username_3**: In my case, this was the issue. As I was still new to Azure DevOps, I just assumed that since I was an admin of the project that gave me rights for everything. Turns out, looking at username_2's answer, there was some more setup I had to do but never did: under Project Settings->General->Permissions I realized that I hadn't touched the settings for ANY of groups listed and most of them had their values set to "Not Set". username_2's solution not only fixed the OP's issue (and mine) but made me realize that there were still more permissions to be set up in general.  
  
  ---
  
  ### Answer by username_4 on 2024-06-21. Score: 0
  
  In your DevOps project:
  
  * Project Settings
  * Repos
  * Repositories
  * [ + Create ] (top,dx blue button)
  
  
  ---
  
  