How syncing works
Repository changes bring app text into Malmoi, and publishing sends saved translations back for the development team to review.
How it works
The repository decides which pieces of app text — keys — exist. Malmoi holds the translated values between updates. Each update from the repository replaces the values in Malmoi with the repository's; it does not merge two values or choose a winner. This is a no-merge flow. Automatic updates are held while there are unsent edits or a Malmoi change request (pull request) is still open. Updates come from your repository's workflow on every commit, or from the nightly run once a day.
Publish puts Malmoi's values into a change request (a pull request on GitHub) for the development team to review and merge.
Read When code changes for the incoming direction and Merging the pull request for the return path.
- When code changesRepository updates refresh your project; while there are unsent edits or an open Malmoi pull request, those updates are held.
- Merging the pull requestReview the generated pull request in GitHub and merge it to return translations to your repository.
- Every nightEvery night, Malmoi publishes saved changes or picks up new repository changes for each active project.
- Undo and resyncProject owners can return an edited value to its last published version, or replace project values with the repository's files.
- Check activity in LogsUse Logs to see project activity, inspect changes, and check the outcome of syncing and publishing.