My Github repo uses the following naming convention for it’s language files:
Source files are located in /language/en-GB:
- /language/en-GB/en-GB.file1.ini
- /language/en-GB/en-GB.file2.ini
- etc…
Translated files follow a similar pattern:
- /language/fr-FR/fr-FR.file1.ini
- /language/fr-FR/fr-FR.file2.ini
- etc…
Notice that the language code is included in both the directory structure and the files themselves.
My question is, can this structure be supported by the Github integration?
I tried the following YAML configuration which recognized my source files but did not perform any PRs after more translated strings were added to the project.
git:
filters:
- filter_type: dynamic
file_format: INI
source_language: en-GB
source_files_expression: <dir>/en-GB/en-GB.<file>.ini
translation_files_expression: '<dir>/<lang>/<lang>.<file>.ini'