If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Pushing changes Pushing changes to GitHub as pull request Pushing changes from Hosted Weblate Merge or rebase Interacting with others Lazy commits Processing repository with scripts Pre commit processing

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note: You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed administrators to receive notifications when something goes wrong, for example notifications on failed merge or Django errors. See also: https://docs.djangoproject.com/en/stable/ref/settings/#admins ALLOWED_HOSTS

Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Automatically receiving changes from Bitbucket Automatically receiving changes from GitLab Pushing changes Merge or rebase Interacting with others Lazy commits Pre commit processing of translations Example - generating administrators to receive notifications when something goes wrong, for example notifications on failed merge or Django errors. See also https://docs.djangoproject.com/en/1.6/ref/settings/#admins ALLOWED_HOSTS

Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Automatically receiving changes from Bitbucket Automatically receiving changes from GitLab Pushing changes Merge or rebase Interacting with others Lazy commits Pre commit processing of translations Example - generating administrators to receive notifications when something goes wrong, for example notifications on failed merge or Django errors. See also https://docs.djangoproject.com/en/1.6/ref/settings/#admins ALLOWED_HOSTS

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Pushing changes Pushing changes to GitHub as pull request Pushing changes from Hosted Weblate Merge or rebase Interacting with others Lazy commits Pre commit processing of translations Example - generating

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Pushing changes Pushing changes to GitHub as pull request Pushing changes from Hosted Weblate Merge or rebase Interacting with others Lazy commits Processing repository with scripts Post update repository

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note: You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed administrators to receive notifications when something goes wrong, for example notifications on failed merge or Django errors. See also: https://docs.djangoproject.com/en/1.8/ref/settings/#admins ALLOWED_HOSTS

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note: You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed administrators to receive notifications when something goes wrong, for example notifications on failed merge or Django errors. See also: ADMINS setting documentation ALLOWED_HOSTS If you are running Django

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed Pushing changes Pushing changes to GitHub as pull request Pushing changes from Hosted Weblate Merge or rebase Interacting with others Lazy commits Processing repository with scripts Post update repository

If you are an owner of some project, you will always receive some important notifications, like merge failures or new language requests. Note: You will not receive notifications for actions you’ve done Weblate supports both export and import of translation files. This allows you to work offline and then merge changes back. Your changes will be merged within existing translation (even if it has been changed administrators to receive notifications when something goes wrong, for example notifications on failed merge or Django errors. See also: ADMINS setting documentation ALLOWED_HOSTS If you are running Django