Hey,
so we created a new branch in cockpit[1], for we want to track translations separately. However, we want to have this new component (branch) connected to the master component. I know it is possible to create linked component, but could not find it. Can someone please advise me?
Thank you! MM
[1] https://translate.fedoraproject.org/projects/cockpit/
Not sure how Michal have done it but you can see a working integration here: https://hosted.weblate.org/projects/phpmyadmin/
It was probably configured by Michal who is in charge (or at least was) of this project. Yaron Shahrabani
<DevOps - Hebrew translator>
On Thu, Jan 23, 2020 at 2:32 PM Matej Marusak mmarusak@redhat.com wrote:
Hey,
so we created a new branch in cockpit[1], for we want to track translations separately. However, we want to have this new component (branch) connected to the master component. I know it is possible to create linked component, but could not find it. Can someone please advise me?
Thank you! MM
[1] https://translate.fedoraproject.org/projects/cockpit/
--
Matej Marušák
Software Engineer
Red Hat
https://www.redhat.com https://red.ht/sig _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
Le 2020-01-23 13:32, Matej Marusak a écrit :
Hey,
so we created a new branch in cockpit[1], for we want to track translations separately. However, we want to have this new component (branch) connected to the master component. I know it is possible to create linked component, but could not find it. Can someone please advise me?
This is part of component configuration: https://docs.weblate.org/en/weblate-3.10.3/admin/projects.html#component-con...
Source code repository VCS repository used to pull changes, see Accessing repositories for more details. This can either be a real VCS URL or weblate://project/component indicating that the repository should be shared with another component. See Weblate internal URLs for more details.
So, in your situation, on the rhel-8-2 component: replace: git@github.com:cockpit-project/cockpit-weblate.git by: weblate://cockpit/master
Jean-Baptiste
On Fri, Jan 24, 2020 at 10:29 AM Jean-Baptiste Holcroft < jean-baptiste@holcroft.fr> wrote:
Le 2020-01-23 13:32, Matej Marusak a écrit :
Hey,
so we created a new branch in cockpit[1], for we want to track translations separately. However, we want to have this new component (branch) connected to the master component. I know it is possible to create linked component, but could not find it. Can someone please advise me?
This is part of component configuration:
https://docs.weblate.org/en/weblate-3.10.3/admin/projects.html#component-con...
Source code repository VCS repository used to pull changes, see Accessing repositories for more details. This can either be a real VCS URL or weblate://project/component indicating that the repository should be shared with another component. See Weblate internal URLs for more details.
So, in your situation, on the rhel-8-2 component: replace: git@github.com:cockpit-project/cockpit-weblate.git by: weblate://cockpit/master
I see, but would it then push updates into rhel-8-2 branch in https://github.com/cockpit-project/cockpit-weblate ?
MM
Jean-Baptiste _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
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.
For you it has no impact.
On Sat, Jan 25, 2020 at 9:26 AM Jean-Baptiste jean-baptiste@holcroft.fr wrote:
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.
For you it has no impact. _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
On Sat, Jan 25, 2020 at 12:51 PM Matej Marusak mmarusak@redhat.com wrote:
On Sat, Jan 25, 2020 at 9:26 AM Jean-Baptiste jean-baptiste@holcroft.fr wrote:
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
[1] https://github.com/cockpit-project/cockpit-weblate/commit/6115a08 [2] https://github.com/cockpit-project/cockpit-weblate/commit/767eefe
For you it has no impact. _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
--
Matej Marušák
Software Engineer
Red Hat
Ah and one more thing. It seems that when I set 'Source code repository' to 'weblate://cockpit/master' then I cannot specify branch ('Repository branch - Option is not available for linked components'). So then it won't have any idea which branch it should push to. So I guess we don't actually want linked component? But is there syncing between components?
Thanks MM
On Sat, Jan 25, 2020 at 9:26 AM Jean-Baptiste jean-baptiste@holcroft.fr wrote:
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.
For you it has no impact. _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org