Merge pull request #9751 from nextcloud/bugfix/noid/docker-ci-issue-template-is-better-then-duplicating

fix(l10n): Refer to the docker-ci issue template only
This commit is contained in:
Marcel Klehr 2023-03-09 15:06:21 +01:00 committed by GitHub
commit 55e8a335b4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -297,7 +297,7 @@ You can invite it from your repository settings:
``https://github.com/<user-name>/<repo-name>/settings/access``
After sending the invitation, please `open a ticket <https://github.com/nextcloud/docker-ci/issues>`_ requesting access.
After sending the invitation, please `open a ticket using the "Request translations" template <https://github.com/nextcloud/docker-ci/issues/new/choose>`_.
The bot will run every night and only push commits to the following branches branch once there is an update to the translation:
@ -326,16 +326,9 @@ That would sync the translations for the branches (``main`` and ``master`` are a
but that is only possible for repositories owned by organizations.
You can `create your own organization <https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch>`_
For the sync job there is a `configuration file <https://github.com/nextcloud/docker-ci/blob/master/translations/config.json>`_
available in our docker-ci repository. Adding there the repo owner and repo name
to the section named **app** via pull request is enough. Once this change is in
one member of the sysadmin team will deploy it to the sync server and the job
will then run once a day.
If you need help then just `open a ticket with the request <https://github.com/nextcloud/docker-ci/issues/new>`_
If you need help just `open a ticket with the request <https://github.com/nextcloud/docker-ci/issues/new/choose>`_
and we can also guide you through the steps.
Manual translation
^^^^^^^^^^^^^^^^^^