Skip to content

Commit ad8a38b

Browse files
authored
docs: Use branch, not tags, for translations
Adds a recommendation to use the release branch ("release/<name>") as opposed to the tag ("release/<name>.x") when pulling translations, to get the most recent ones.
1 parent b7ad5df commit ad8a38b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/configuration.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -397,7 +397,7 @@ Tutor builds images with the latest translations using the ``atlas pull`` `comma
397397
By default the translations are pulled from the `openedx-translations repository <https://github.com/openedx/openedx-translations>`_
398398
from the ``ATLAS_REVISION`` branch. You can use custom translations on your fork of the openedx-translations repository by setting the following configuration parameters:
399399

400-
- ``ATLAS_REVISION`` (default: ``"main"`` for Tutor Main, or ``"{{ OPENEDX_COMMON_VERSION }}"`` if a named release is used)
400+
- ``ATLAS_REVISION`` (default: ``"main"`` for Tutor Main, or ``"{{ OPENEDX_COMMON_VERSION }}"`` if a named release is used). Note that if you're running on a point release (for example, ``release/ulmo.1``), you will not be able to pull any upstream additions to translations - they will be "frozen" at that Git tag. If you're making changes to your language on Transifex, it is recommended to set this value to the Git branch (for example, ``release/ulmo``) to pick up any new translations that occur for that release.
401401
- ``ATLAS_REPOSITORY`` (default: ``"openedx/openedx-translations"``). There's a feature request to `support GitLab and other providers <https://github.com/openedx/openedx-atlas/issues/20>`_.
402402
- ``ATLAS_OPTIONS`` (default: ``""``) Pass additional arguments to ``atlas pull``. Refer to the `atlas documentations <https://github.com/openedx/openedx-atlas>`_ for more information.
403403

@@ -535,4 +535,4 @@ Then, restart your platform::
535535
That's it! You can send a test email with the following command::
536536

537537
$ tutor local run --no-deps lms ./manage.py lms shell -c \
538-
"from django.core.mail import send_mail; send_mail('test subject', 'test message', 'YOURUSERNAME@gmail.com', ['YOURRECIPIENT@domain.com'])"
538+
"from django.core.mail import send_mail; send_mail('test subject', 'test message', 'YOURUSERNAME@gmail.com', ['YOURRECIPIENT@domain.com'])"

0 commit comments

Comments
 (0)