-
Notifications
You must be signed in to change notification settings - Fork 34
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add instructions to docs about testing translations
I just learned how to do this, so it's helpful to tell other's how!
- Loading branch information
1 parent
fb82f1c
commit db726a7
Showing
1 changed file
with
25 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# How to Specify Translation Source | ||
|
||
When adding a language or testing translation updates, it can be useful to see changes in the devapp. Follow the steps bellow to point your devapp to a specific branch for translations. | ||
|
||
In the GitHub CLI for your e-mission-phone repo, navigate into the locales folder: | ||
|
||
`cd locales` | ||
|
||
Clear the remote tracking, and set the appropriate upstream and origin repositories: | ||
|
||
`git remote rm origin` | ||
|
||
`git remote add upstream https://github.com/e-mission/e-mission-translate` | ||
|
||
`git remote add origin https://github.com/[your_account]/e-mission-translate` | ||
|
||
Check what has been set: | ||
|
||
`git remote -v` | ||
|
||
Checkout the branch you wish to test | ||
|
||
`git checkout --track origin/[branch_to_test]` | ||
|
||
Now, the translations you see in the emulator will be pulled from that branch, and your edits in locales can be pushed into your fork/branch of translations. |