File repository wiki

Content that you already maintain in a Git repository can be published to a wiki. You can publish multiple wikis within a single team project. For information about managing the different wiki types, see Differences between provisioned wiki and publish code as wiki.

You can add and edit content you've published to a wiki using the steps outlined in this article. Or, you can also work offline and update wiki content in the same way you collaborate on code through a Git repository. For more information, see Update wiki pages offline. Begin by connecting to your project using a supported web browser and choose Wiki. If you need to switch your team project, choose Azure DevOps to browse all team projects and teams.

Choose this option when you maintain Markdown files in an existing Git repo and you want to publish them to a wiki. The Publish code as Wiki option won't appear if your project doesn't have a Git repository defined. Create a new Git repo , and then return and refresh this page. If you've already provisioned a team project wiki, from the context menu for Wikis, choose Publish code wiki.

Choose the repository, branch, and folder that contain the Markdown files and name the wiki repository. The Git repo must be within the team project. Specify the root of the repository when you want to publish all Markdown files in the repository to your wiki.

Choose Publish. The wiki repo is populated with the Markdown files and folders included within the repo you selected. For example, the following image shows the published repo for the files that are contained in the azure-docs-sdk-node repository that you selected in Step 2.

A parent page for each subfolder defined within the published folder, even if it doesn't contain any Markdown files. The head of the Git repo branch is now mapped to the wiki.

Any changes made within the branch and selected folder s are automatically reflected in the Wiki. There are no other workflows involved. For the Wiki that's provisioned with the Markdown files you've added, you can now add or edit pages in the same way that you maintain code in your Git repository. You can publish a Git repository to a wiki with the az devops wiki create command.

Run this command when you maintain Markdown files in an existing Git repo and you want to publish them to a wiki. You can't publish code as Wiki if your project doesn't have a Git repository already defined. If necessary, create a new Git repo , and then return to this page. For Azure DevOps Server , you can use the following command to set the default server instance, collection, and project. The wiki is published in the wikis folder in the main branch and the result is shown in table format.

Choose the page you want, select Actions , and then choose the operation that you want. You can manage your wiki repo in the same way you manage any other Git repo by defining branch policies on the branch that you selected to publish to a wiki. However, without any policies defined, you can make changes and push them directly to the branch from your web portal or from a client. You can use the links available in edit mode to preview your changes or highlight changes made from the previous version.

Git and GitLab both support paths exceeding those limits. However, if your file system enforces these limits, you cannot check out a local copy of a wiki that contains filenames exceeding this limit. To prevent this problem, the GitLab web interface and API enforce these limits: bytes for page titles reserving 10 bytes for the file extension. While you can still create files locally that exceed these limits, your teammates may not be able to check out the wiki locally afterward.

Edit a wiki page You need at least the Developer role to edit a wiki page: On the top bar, select Menu. Go to the page you want to edit, and either: Use the e wiki keyboard shortcut.

Select the edit icon. Edit the content. Select Save changes. For an example, read Table of contents. Delete a wiki page You need at least the Developer role to delete a wiki page: On the top bar, select Menu. Go to the page you want to delete. Select Delete page. Confirm the deletion.

Move a wiki page You need at least the Developer role to move a wiki page: On the top bar, select Menu. Go to the page you want to move. Add the new path to the Title field. The page author. The commit message. The last update.

Previous revisions, by selecting a revision number in the Page version column. To view the changes for a wiki page: On the top bar, select Menu. Go to the page you want to view history for.

Select Page history. View changes between page versions Introduced in GitLab You can see the changes made in a version of a wiki page, similar to versioned diff file views: On the top bar, select Menu. Select Page history to see all page versions. Track wiki events Version history Introduced in GitLab Git events were introduced in GitLab Feature flag for Git events was removed in GitLab GitLab tracks wiki creation, deletion, and update events. These events are displayed on these pages: User profile.

Activity pages, depending on the type of wiki: Group activity. Project activity. Commits to wikis are not counted in repository analytics. Customize sidebar Introduced in GitLab You need at least the Developer role to customize the wiki navigation sidebar. In the top right corner of the page, select Edit sidebar. When complete, select Save changes. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful?

Please rate your experience Yes No. Any additional feedback? You must have a team project. If you don't have a team project yet, create one in Azure DevOps. You must have at least Basic access to create and modify a wiki. You must have the permission Create Repository to publish code as wiki.

By default, this permission is set for members of the Project Administrators group. Anyone who is a member of the Contributors security group can add or edit wiki pages.

Anyone with access to the team project, including stakeholders , can view the wiki. If you don't have a team project yet, create one on-premises. Note For Azure DevOps Server , you can use the following command to set the default server instance, collection, and project.

Example Open a wiki named 'myprojectwiki'.