Describe the solution you'd like
We have two projects that share translations. In this case it's an Android and an iOS app, but it could also be backend and frontend of some kind. The projects are located in two different repositories and the file formats are different.
This could be solved by having a 1:n relationship between components and version control systems, and a 1:1 relationship between version control and file configuration.
Describe alternatives you've considered
A valid workaround is to only have one repository and import the translation files as a download with a different format from the second project via some task runner.
You can share repositories inside Weblate, see https://docs.weblate.org/en/latest/vcs.html#weblate-internal-urls (in fact Weblate does this automatically in case you add existing repo again).
@nijel I want the opposite: Multiple repositories per component.
Edit: I want to share translations between repositories, not the other way round.
One component is always for one file, so that will never work. You can have any number of components within one project.
Maybe https://docs.weblate.org/en/latest/faq.html#how-to-translate-multi-platform-projects would be helpful to you as well.
@nijel just tried to set this up for @amiuhle
Is translation propagation supposed to update all ocurrences of the given key in all components of a project?
I get only a suggestion

It works only on translating, I've recently explained it here: https://github.com/WeblateOrg/weblate/issues/3166#issuecomment-551064246
Probably time to put this into the docs :-)
Thanks for your response. :-)
Most helpful comment
It works only on translating, I've recently explained it here: https://github.com/WeblateOrg/weblate/issues/3166#issuecomment-551064246
Probably time to put this into the docs :-)