3 ms·

They are code files managed by a different set of people (translators), not generated artifacts (as they explain elsewhere in this discussion). If we are being

They are code files managed by a different set of people (translators), not generated artifacts (as they explain elsewhere in this discussion). If we are being pedantic, git was not designed to host multiple projects in a single repo (otherwise, git would have been a subdirectory in the kernel tree). But tools are made without knowing how they'll be used, and that's ok, so I wouldn't stress on what the purpose for monorepo was, but how it's used and what value it brings.

prmoustache 4y ago
>They are code files managed by a different set of people (translators), not generated artifacts (as they explain elsewhere in this discussion Translations do not look like code to me. Rather human generated artifacts. What I understand is there is a strong tie/match needed between versions of these translations files and the code itself, so I believe this is where having all in the same repo would make sense, having the translators update those file when code has been modified...