Creating a Pull Request
A pull request asks maintainers to review and merge your changes into the wiki.
From the Wiki Website
Best for small edits to one page.
- Open the page on the wiki site
- Click Edit this Page at the bottom
- Make your changes on GitHub
- Click Commit Changes and fill in a short commit message
- Open a pull request against
mainusing the title and description format below
From Your Computer
Best for new pages, media, or changes across multiple files. You can set up a local preview after cloning.
- Fork pokewalker-wiki on GitHub, then clone your fork:
sh
git clone https://github.com/YOUR-USERNAME/pokewalker-wiki
cd pokewalker-wikiReplace YOUR-USERNAME with your GitHub username.
- Create a branch for your work (you cannot commit straight to
main):
sh
git checkout -b your-change-name- Make your edits under
wiki/(andpublic/if you add visual content)- Make sure to follow the Style Guidelines!
- Commit your changes with a clear message:
sh
git add .
git commit -m "Short description of the change"- Push your branch:
sh
git push -u origin your-change-name- Open GitHub and create a pull request into
main - Fill in the title and description using the format below
Pull Request Conventions
Title
Use a short conventional commit prefix, then a clear name for what changed:
| Prefix | When to use | Example |
|---|---|---|
feat: | New or updated documentation | feat: add teardown images to hardware |
fix: | Corrects wrong or broken docs | fix: correct instruction cycle count |
refactor: | Restructures docs without changing meaning | refactor: reorganize ghidra docs |
Keep the title specific. Prefer feat: add timer breakdown page over feat: update page.
Description
Write enough for a maintainer to understand the change without needing to open every file.
- What you added, changed, or removed
- Which pages or sections are affected
- Why the change was needed, if it is not obvious
Example:
md
- Adds an RTC page under Hardware with register docs and behavior info.