Hi, I would like to create a translation component that will track 1.2.x branch of authselect. I find Weblate still quite confusing so I need to ask: How can I do that?
I remember setting some options on existing components. Is it possible to copy all the components and just change the branch name so I don't have to set the options again?
https://translate.fedoraproject.org/projects/authselect
Thanks, Pavel
On 2022-04-29 16:05, Pavel Březina wrote:
Hi, I would like to create a translation component that will track 1.2.x branch of authselect. I find Weblate still quite confusing so I need to ask: How can I do that?
I remember setting some options on existing components. Is it possible to copy all the components and just change the branch name so I don't have to set the options again?
https://translate.fedoraproject.org/projects/authselect
Thanks, Pavel
Hi Pavel,
You can add a new translation component, then choose "From existing component".
On 4/29/22 16:16, darknao wrote:
On 2022-04-29 16:05, Pavel Březina wrote:
Hi, I would like to create a translation component that will track 1.2.x branch of authselect. I find Weblate still quite confusing so I need to ask: How can I do that?
I remember setting some options on existing components. Is it possible to copy all the components and just change the branch name so I don't have to set the options again?
https://translate.fedoraproject.org/projects/authselect
Thanks, Pavel
Hi Pavel,
You can add a new translation component, then choose "From existing component".
Thank you, I managed to add new branch using "Additional branch" instead, however it only offered *-application and not the other components (the same happens for "From existing component").
There are also *-adoc that are linked to master-application, how can I add these?
Thanks, Pavel
On 2022-05-03 11:48, Pavel Březina wrote:
Thank you, I managed to add new branch using "Additional branch" instead, however it only offered *-application and not the other components (the same happens for "From existing component").
There are also *-adoc that are linked to master-application, how can I add these?
There is an add-on called "Component discovery" (Manage > Add-ons) that you can enable in your 1.2.x-application component. You can use the same settings as the other one, but you may need to adapt the generated component name to something like "1.2.x-{{ component }}"
On 5/3/22 23:23, darknao wrote:
On 2022-05-03 11:48, Pavel Březina wrote:
Thank you, I managed to add new branch using "Additional branch" instead, however it only offered *-application and not the other components (the same happens for "From existing component").
There are also *-adoc that are linked to master-application, how can I add these?
There is an add-on called "Component discovery" (Manage > Add-ons) that you can enable in your 1.2.x-application component. You can use the same settings as the other one, but you may need to adapt the generated component name to something like "1.2.x-{{ component }}"
Thank you, this did the trick. The newly created component did not inherit the addons so I had to set it manually.
Last question, is it possible to add target branch to the GitHub pull request title so I can differentiate between them more easily?
Translations update from Fedora Weblate -> Translations update from Fedora Weblate (1.2.x)
I was able to only find how to change commit messages.
Thanks, Pavel
On 2022-05-04 13:21, Pavel Březina wrote:
Last question, is it possible to add target branch to the GitHub pull request title so I can differentiate between them more easily?
Translations update from Fedora Weblate -> Translations update from Fedora Weblate (1.2.x)
I was able to only find how to change commit messages.
I think the title of the PR is the first line in the 'Merge request message' field you can find in Settings > Commit messages. You should be able to use something like {{ component_remote_branch }} or {{ component_name }} in it.
-
darknao -
Pavel Březina