push issues

Jump to navigation Jump to search

Please summarize the below thread in the editing box. You may use any wikitext in your summary. When you finish, click "Publish changes".

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.


You can view and copy the source of this page.

Return to Summary:Support/push issues.

push issues

Hi,

We would like to have TranslateWiki not to push in our master branch but in different one. Is this possible?

In addition, are you using forced push in any of your push actions?

Thanks

Haniavis (talk)10:53, 8 August 2018

Why not use master? What process will you use to ensure continuous localisation (for instance, how are you going to update source messages and bring translations to master)?

Nemo (talk)11:03, 8 August 2018

Because we use master for our automatic update of our deployments. And when you push to master, our users see that there is an update which they pull, but never understand what was that.

We need to handle this pushing of translations to master, we will manually merge your new branch with master when there is translations.

Haniavis (talk)16:37, 23 August 2018

Experience shows that doing merges manually adds work for developers and translators while lowering the quality of both code and translations. Deploying translations immediately is good. What is the concrete problem you see?

Nemo (talk)16:52, 23 August 2018
 
 

We never use forced push. We can export to a different branch from which we read from, but that means it is you must deal with merge conflicts. In our experience that often doesn't work (translation updates not getting applied in a timely manner), so that's why we recommend against it.

Nike (talk)08:01, 27 August 2018