lokalise-ci-integration

# Lokalise CI Integration ## Overview Automate the full translation lifecycle through GitHub Actions: upload source strings when code is pushed, download translations during builds, block PRs with missing translations, and manage branch-based translation workflows that mirror your Git branching strategy. The goal is zero manual translation file management — developers write code, translators work in Lokalise, and CI keeps everything in sync. ## Prerequisites - Lokalise project with Project ID (Settings > General > Project ID) - Lokalise API token with read/write permissions (Profile > API Tokens), stored as `LOKALISE_API_TOKEN` GitHub secret - `LOKALISE_PROJECT_ID` stored as GitHub secret (or variable) - Lokalise CLI v2 (`lokalise2`) — installed in CI via `curl -sfL https://raw.githubusercontent.com/nicktomlin/lokalise-cli-2-install/master/install.sh | sh` - Source locale files committed to the repository (e.g., `src/locales/en.json`) ## Instructions ### Step 1: Upload Source Strings on Push Create `.github/workflows/lokalise-upload.yml` to push source strings to Lokalise whenever the default locale file changes on `main`: ```yaml name: Upload translations to Lokalise on: push: branches: [main] paths: - 'src/locales/en.json' # Adjust to your source locale path jobs: upload: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Install Lokalise CLI run: | curl -sfL https://raw.githubusercontent.com/...