I think so yes. Otherwise, it would be a bug.
I never used linked repository for multiple git branches.
The only usage for linked component is to make weblate faster.
It means weblate will have one single git repository on disk instead of many.
I thought that the main advantage of linked components is that, if you translate some string in one component and the same string is in the other component as well, it would get translated in both.
As we have branches, it means they now share all the string, and in the time they diverge. And it would be pointless work for translators to translate the exact same strings in two components.
So I did some experimenting, and I thought someone else might be interested as well, so here is how it works:
I kept the original setting, as 'linked' was not what I really needed.
I changed some strings in `cockpit/master`. When I went to `cockpit/rhel-8-2` these strings were updated there automatically as well.
And when I synced both `cockpit/master` and `cockpit/rhel-8-2` into our github, both branches in github were updated with separate commits [1][2].
So sync between components works as expected even when components are not linked.
MM
--
Matej Marušák
Software Engineer
Red Hat