As both branches share the same files (and the ja
branch only adds translations) I would suggest merging master
into ja
regularly.
You basically first merge new changes of master into your translation branch. This should work without problems as your translation branch does not change the original files.
Afterwards you can use git diff HEAD^
or git show -m
to view the new changes and add another commit with your translations.
If you want to check for untranslated commits you then can do git fetch; git log -p ja..origin/master
, which shows you all commits on the remote master, which you did not already merged into your local ja
branch.
Of course this cannot check if you really translated everything correctly, but it allows you to do something like git log -p -m --first-parent
to manually check for yourself. This should alternately show a translated diff (by you) and an untranslated commit (from the merge).
You can also do git fetch; gitk --all
to get a visual impression what is going on.
This would result in a graph like this:
→ M → T → M → T → M → T → (ja)
↑ ↑ ↑
→ O → O → O → (master)
Where O
is one original commit M
is the merge and T
is the translation commit.
You could also add the translation directly into the merge commit to have only one single (merge) commit for each original commit, but maybe having two seperate commits might be a bit clearer.