If I had a Git repo containing text, and wanted to maintain separate branches for different language versions of that same text, is there a good workflow/process which would require any change to the main branch to be reviewed (i.e. translated) when it's merged to another branch?
I'm still skeptical that it's definitively the right way, and storing entirely different content on different branches makes me uneasy, but they're never intended to (re)converge, which makes me think it's actually fine. The branches will all share the same file structure.
-
-
Software is just a tool and you can use it however you want. The only reason it matters how the tool was intended to be used is as a predictor of how bumpy the ride will be.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.