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?
-
Show this thread
-
Replying to @propensive
I would create a new org and have a different repo for each language as this way what’s available is more visible with normal tools
1 reply 0 retweets 0 likes
Replying to @SalarRahmanian
I should have explained a bit more context that I'm writing my own tool which will put some additional constraints on the structure of the text, while the tool might also be able to help with managing the translations...
2:15 AM - 1 Nov 2019
0 replies
0 retweets
1 like
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.