![]() 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. When you create a new project and navigate to the wiki page, you are now greeted with this screen. If the team using it is mature enough to use it as a normal repository, then why limit its use? Current Wiki creation It would be better if a Project Admin could choose to include the repository in the normal overview or not. Note: I find the two types very confusing for the user and there is not a clear way to use them the same way. This is no longer the case.Ĭurrently 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. 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. If you created a wiki a couple of years ago, you have the first wiki type. Publish one or more repositories as a wiki.The default (old) way of creating a wiki.In Azure DevOps there is a distinction between two ways to setup your wiki: ![]() Short version: it is not available anywhere, but you can ‘guess’ the correct URL and navigate to it: Of course, I was intrigued and started to search: this functionality was always there before, so surely this will still be available? 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. Weirdly enough, we couldn’t find how to get the repo to be visual so we could use it. This used to be available if you knew what to do, so you could clone the repo and add pages programmatically for example. Today someone in the Azure DevOps Club slack asked a question about finding the repo from the default wiki in Azure DevOps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |