Sharing Translations across multiple repositories

[LorisSigrist]

A question we currently don't have an answer to is how people can use the same set of translations across multiple repositories. This would be required if the fronted and backend of a site are in separate repos.

Do we just force users to have a monorepo? That would drive up adoption-friction quite significantly.

Of course, if multiple repos use the same inlang project, we immediately run into sync-issues again. The whole point of storing translations in git (lix) is to avoid this.

• Edit message in Repo A on a development branch. Does repo B see it?
• How does repo B create a development branch with the same messages as a development branch in repo A.
• The rest of Pandoras box

One thing that might work is to have the inlang-project in it's own repo & then use that as a submodule in each repo that uses it.

I would love to get some perspectives on this. I'm not saying we have to support this, I'm saying we should have an answer ready.

[samuelstroschein]

why do they want to share translations? see opral/inlang-sdk#7

Off-topic: everything should be in "one repo" with "submodules" in lix (git's repo approach completely messed up)