Determine and implement the best way to include the translations repository
Options:
- Keep the way it is now: translations are cloned at every build, but updates on the translations itself does not trigger a pipeline.
- Use i18n as a Git submodule so updates trigger CI. But then who would keep the submodule updated?
- Use a daily scheduled pipeline to clone i18n, check if there's any changes, and build if needed (both for GitLab and GitHub mirrors).
- Any other alternatives...
Also:
-
Make sure to invoke check_po_status.py in the build step to ensure the landing pages are rebuilt only if no major l10n issues exists. The current check_po_status.py and other Q&A scripts have a different use case than invocation by CI/CD jobs.
Edited by Silvio Rhatto