Weblate Setup with Git Integration
Budget: €30 – €250 EUR
We have a private GitHub repository that already contains translations for multiple languages. The translations use standard gettext structure:
translations/<language>/LC_MESSAGES/messages.po
translations/messages.pot
Example:
translations/cs/LC_MESSAGES/messages.po
translations/de/LC_MESSAGES/messages.po
translations/pl/LC_MESSAGES/messages.po
We deployed a new Weblate instance (Docker/Helm) and created a new project and component. We configured the Git repository URL, branch (master), file mask (translations/*/LC_MESSAGES/messages.po), translation template, and added Weblate’s SSH deploy key to GitHub with write access. Weblate connects to the repository without errors.
However, Weblate does not detect any existing translations. It shows the message “No file mask matches”, even though the .po files exist in the repository. As a result, Weblate does not import or display any languages or translation strings.
translations/<language>/LC_MESSAGES/messages.po
translations/messages.pot
Example:
translations/cs/LC_MESSAGES/messages.po
translations/de/LC_MESSAGES/messages.po
translations/pl/LC_MESSAGES/messages.po
We deployed a new Weblate instance (Docker/Helm) and created a new project and component. We configured the Git repository URL, branch (master), file mask (translations/*/LC_MESSAGES/messages.po), translation template, and added Weblate’s SSH deploy key to GitHub with write access. Weblate connects to the repository without errors.
However, Weblate does not detect any existing translations. It shows the message “No file mask matches”, even though the .po files exist in the repository. As a result, Weblate does not import or display any languages or translation strings.