Does this action work for monorepos?

[lfloyd117]

We have a monorepo of Node apps that all have their own crowdin.yml config file.
As far as I can tell, this action expects a root crowdin.yml for a single project, correct? If we want to handle a monorepo, we would need to do things manually, yes?

[andrii-bodnar]

Hi @lfloyd117,

The Crowdin GitHub Action is project structure agnostic and can work with any project layout. For multiple crowdin.yml files, you can create separate workflow steps and use the config option to specify each configuration file path:

jobs:
  sync-project-a:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Crowdin Action for Project A
        uses: crowdin/github-action@v2
        with:
          config: 'path/to/project-a/crowdin.yml'
          upload_sources: true
          download_translations: true
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID_A }}
          CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN_A }}

  sync-project-b:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Crowdin Action for Project B
        uses: crowdin/github-action@v2
        with:
          config: 'path/to/project-b/crowdin.yml'
          upload_sources: true
          download_translations: true
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID_B }}
          CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN_B }}

Each step uses its own crowdin.yml file via the config option, allowing independent management of different projects within the same repository.