mika/pokerogue
1
0
Fork 0
mirror of https://github.com/pagefaultgames/pokerogue.git synced 2025-07-03 23:12:20 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update localization.md to remove unneeded step

Browse Source
This commit is contained in:
Bertie690 2025-07-02 15:35:29 +02:00 committed by GitHub
parent d675a6a406
commit 9c09d2cf4d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/localization.md
View File

@ -28,18 +28,19 @@ The parent repo (the "superproject") houses a cloned version of the 2nd reposito
> >
> ![Image showing Visual Studio Code's Source Control tab. A separate dropdown can be seen for each individual submodule.](https://github.com/user-attachments/assets/8b4d3f64-aec1-4474-91df-03dc1252a2fa "Making commits on submodules without even changing directories!") > ![Image showing Visual Studio Code's Source Control tab. A separate dropdown can be seen for each individual submodule.](https://github.com/user-attachments/assets/8b4d3f64-aec1-4474-91df-03dc1252a2fa "Making commits on submodules without even changing directories!")
From the perspective of the main project, the locales submodule is fairly simple to work with, but there are some important commands to keep in mind. From the perspective of the main project, the locales submodule is fairly simple to work with.
## Fetching Changes from Submodules ## Fetching Changes from Submodules
Once you have set up your fork, run the following command to initialize your branch's locales repository and update its HEAD: The following command will initialize your branch's locales repository and update its HEAD:
```bash ```bash
git submodule update --init --recursive git submodule update --init --recursive
``` ```
This is run automatically after merging or switching branches, so you _usually_ won't have to run it yourself after the first time. > [!INFO]
> This is run _automatically_ after cloning, merging or changing branches, so you should rarely have to run it manually.
> [!WARNING] > [!WARNING]
If you run into issues with your development environment afterwards, try deleting the `.git/modules/public` and `public/locales` folders before re-running the command. > If you run into issues with the `locales` submodule, try deleting the `.git/modules/public` and `public/locales` folders before re-running the command.
## How Are Translations Integrated? ## How Are Translations Integrated?