I’m working on a ASCIIDOC project (in Crowdin Enterprise/Github Enterprise) with a shared repo in which we host common/frequently used snippets like warnings or handling instructions.
English is our master (“main”) branch; we’d like to have other languages in branches like “main-es” for Spanish, where the translated files shall have the same file name as the source files to ease integration and skip rework of links in the main-documents to the respective languages.
How do I tell Crowdin to “overwrite the source files for that new branch”?
Or do you have other approaches to a similar situation?
Achieving this setup is possible, though it requires a few adjustments to how your integration is configured.
First, you will need to manually create all the necessary target language branches, such as “main-es,” directly within GitHub Enterprise, as the Crowdin integration cannot create new branches on its own.
Once those branches are ready, you will need to change the integration settings to operate in “Target File Bundles” mode. This mode allows you to create custom file bundles within Crowdin, where you can explicitly specify which language bundles should be delivered to which corresponding branch.
However, please keep in mind: Target File Bundles mode functions strictly as a translation-export-only mechanism. While it will push your translated files directly to your designated language branches, the integration will no longer automatically pull source files from the repository in this mode. You will just need to manage the source file updates separately.