Missing wiki repository in Azure DevOps

24 Jul, 2020
Xebia Background Header Wave

Today someone in the Azure DevOps Club slack asked a question about finding the repo from the default wiki in Azure DevOps. This used to be available if you knew what to do, so you could clone the repo and add pages programmatically for example. Weirdly enough, we couldn’t find how to get the repo to be visual so we could use it. In this case, the person asking the question wanted to add branch policies on the wiki repo so they can enforce Pull Requests on incoming changes. Of course, I was intrigued and started to search: this functionality was always there before, so surely this will still be available?

Picture of a dog (Pugg) with 'stress'

Photo by Matthew Henry)


Short version: it is not available anywhere, but you can ‘guess’ the correct URL and clone it: git clone <a href=";organization&gt;/&lt;project&gt;/_git/&lt;name"><a href=";organization&gt;/&lt;project&gt;/_git/&lt;name"><a href=";organization&gt;/&lt;project&gt;/_git/&lt;name"><organization>/<project>/_git/<name</a></a></a> of wiki>.wiki

Wiki types

In Azure DevOps there is a distinction between two ways to setup your wiki:

  1. The default (old) way of creating a wiki. It is a Git repo under the covers
  2. Publish one or more repositories as a wiki. You can find more documentation here


If you created a wiki a couple of years ago, you have the first wiki type. You could get the git URL to clone the repo and when you made changes to it, the repository would become visible on the Repos overview. This is no longer the case.

Currently when you create a new team project, you get the option to choose between the two types, although it is not very clear to see the difference between the two.

Note: I find the two types very confusing for the user and there is not a clear way to use them the same way. It would be better if a Project Admin could choose to include the repository in the normal overview or not. If the team using it is mature enough to use it as a normal repository, then why limit its use?

Current Wiki creation

When you create a new project and navigate to the wiki page, you are now greeted with this screen. Already confusing and the Learn more link tries to make the difference more clear, but doesn’t really make it clear it will always be a repo underneath. New project screen

I mean, if you need this large a matrix to try and make the differences clear, while under the covers it is the same setup, why not make your product easier to use?

Difference matrix screenshot from the docs

Searching for the repo

Testing things out, I created a new team project [Demo] and created a new project wiki for it. Then I started searching for the wiki in the repos overview, but it only shows the default, empty project repository, not the wiki repo:

Azure Repos dropdown that doesn't show the wiki repo, only the default

If you go to the wiki, it shows the name of the wiki:

New wiki created with wiki name highlighted

Even the dropdown or extra button (the three dots) doesn’t some more information. You can find the git URL for cloning you need, but not how to get to the repository to set up branch policies for example…


Azure DevOps has an awesome REST API you can use to automate almost everything in Azure DevOps, so let’s see what it returns.

If you update the URL in your browser, you can test the API with normal GET request without setting up to much stuff. Go to <a href=""><a href=""><a href=""></a></a></a> (so organization/project/_apis/git/repositories) and you get a list of repositories.

Note this does not include the wiki repo, only the default empty repo with the same name as the project.

Include Hidden repositories

If you include the query string includeHidden=True as can be found in the API docs, you see that the wiki repo is visible:

Conclusion: it is a repo, but a hidden one!

I’ve searched and tested some options, but I didn’t manage to update the repo and make it not hidden anymore.

Finding some really old posts and a GitHub issue that requested the hidden repo to be visible (that got redirected to a UserVoice request that was closed due to inactivity 😧), I figured that this old URL might still be working… And luckily it is!

The fix

If you check the name of your wiki repository, you can enter it in the URL of a normal repository (use the repo selection dropdown first for the correct URL to appear for easy changing): <a href=";organization&gt;/&lt;project&gt;/_git/&lt;name"><a href=";organization&gt;/&lt;project&gt;/_git/&lt;name"><a href=";organization&gt;/&lt;project&gt;/_git/&lt;name"><organization>/<project>/_git/<name</a></a></a> of wiki>.wiki

Wiki repo visible

Note that the dropdown still doesn’t show the wiki repo: it never will currently

The most amazing part: the UI will now remember the last repo you have viewed, so if you use the menu to navigate to branches, it will enable you to set branch policies. You can add the repo to the URL here by hand as well of course, if need be.

Hopefully the Azure DevOps team improves on this omission (in my opinion) soon.


So, in conclusion: if you can’t find the wiki repo in Azure DevOps, you now have a way to get to it, even when the UI doesn’t give you an option for it.

Rob Bos
Rob has a strong focus on ALM and DevOps, automating manual tasks and helping teams deliver value to the end-user faster, using DevOps techniques. This is applied on anything Rob comes across, whether it’s an application, infrastructure, serverless or training environments. Additionally, Rob focuses on the management of production environments, including dashboarding, usage statistics for product owners and stakeholders, but also as part of the feedback loop to the developers. A lot of focus goes to GitHub and GitHub Actions, improving the security of applications and DevOps pipelines. Rob is a Trainer (Azure + GitHub), a Microsoft MVP and a LinkedIn Learning Instructor.

Get in touch with us to learn more about the subject and related solutions

Explore related posts