From 8af6bf851c8793ddb0ab8a6ffabf5e7fd7f9dc7f Mon Sep 17 00:00:00 2001 From: Joas Schilling Date: Thu, 19 May 2022 16:23:25 +0200 Subject: [PATCH] Extend translation docs a bit Signed-off-by: Joas Schilling --- developer_manual/basics/front-end/l10n.rst | 31 +++++++++++++++++++--- 1 file changed, 27 insertions(+), 4 deletions(-) diff --git a/developer_manual/basics/front-end/l10n.rst b/developer_manual/basics/front-end/l10n.rst index ad312fe6e..648c390e5 100644 --- a/developer_manual/basics/front-end/l10n.rst +++ b/developer_manual/basics/front-end/l10n.rst @@ -267,10 +267,33 @@ Add one more file called :file:`.l10nignore` in root of the repository and the f Mostly used to ignore packed js files. Now the GitHub account `@nextcloud-bot `_ needs -to get write access to your repository. It will run every night and only push -commits to the master branch once there is an update to the translation. In general -you should enable the `protected branches feature `_ -at least for the master branch. +to get ``write`` access to your repository. It will run every night and only push +commits to the following branches branch once there is an update to the translation: + +* main +* master +* stableX (X being the recent 3 versions of Nextcloud Server) + +You can overwrite this list by creating a file ``.tx/backport`` in your repository with the following content:: + + develop stable + +That would sync the translations for the branches (``main`` and ``master`` are added automatically): + +* main +* master +* develop +* stable + + +.. note:: + + In general you should enable the + `protected branches feature `_ + for those branches. If you do that, you need to grant the + `@nextcloud-bot `_ ``admin`` permissions, + but that is only possible for repositories owned by organizations. + You can `create your own organization `_ For the sync job there is a `configuration file `_ available in our docker-ci repository. Adding there the repo owner and repo name