Note: This article uses Windows key combinations.
github.dev is a publicly available, GitHub-tailored web version of Visual Studio Code. Compared to GitHub's own web editor, it offers a lot more flexibility and control over the repository's contents. github.dev is a recommended way of contributing to the osu! wiki, especially while working on several articles at once.
Notice
To work with the osu! wiki, fork the ppy/osu-wiki repository.
To open osu! wiki in the editor, replace github.com in the URL of your fork repository with github.dev. Alternatively, open your fork on GitHub and press . (period).
Example use of the command palette
While all menus are accessible from the editor's interface, the intended way of navigation is using the command palette:
F1 and enter the name of a setting to open, or action to perform. If nothing shows up, explore the hamburger menu (≡) in the top left corner of the screen.Ctrl + P and enter its name.After you have read Best practices § Making changes, create a new branch to store your changes in.
F1 and type branch.
Create new branch..., enter the name of the branch, and press Enter.de-modding-v2.Ctrl + P and enter the name of a file you want to open, then press Enter. Loose matching is supported: for example, typing nominators veto en will bring up wiki/People/The_Team/Beatmap_Nominators/Beatmap_Veto/en.md.github.dev.Articles are stored within folders with the original text (en.md) and its translations, which use different language-based file names.
.md file using one of the supported file names./wiki/ directory.en.md file with the article's text to the new folder.Ctrl + Shift + E).Ctrl to select multiple objects.F2.
Commit and push changes to save them permanently
Ctrl + Shift + G).+ button on files you want to save in a single batch.Ctrl + Enter or click the ✓ button to commit and push your changes.When everything is ready, use Best practices § Self-check to proofread your changes. After that, send your changes for review by opening a pull request to the ppy/osu-wiki repository.