Керування версіями
Maintain an agile localization process and avoid translation delays for added texts or new product features. Integrate your project branches with Crowdin and allow translators to access all new texts immediately.
Гілки
Коли над розробкою продуктів працюють кілька людей, галузі допомагають керувати різними версіями вмісту. If you have a continuous project, you can add project branches to Crowdin and allow translators to translate the texts right in parallel with development to avoid deployment delays.
Гілка Crowdin виглядає як звичайна папка, позначена спеціальним значком, з певною поведінкою щодо дублюючих рядків.
Example of branch structure in the version control system (VCS) and Crowdin:
Створення галузі
Note! The first files you upload to the Crowdin project must contain all the original strings and should be placed in the corresponding branch. For all article examples, a branch with original texts is named Master.
There are a few ways to add branches to Crowdin:
- Integrate Crowdin projects with GitLab, GitHub, Bitbucket, or Azure Repos. It’s a recommended option, as branches selected for localization in your version control system (VCS) will be created in Crowdin automatically.
- Use CLI or API to add new branches.
- Create branches manually.
Створіть гілку за допомогою API
To create a branch via API, use the Add Branch method.
Управління галуззю через CLI
If you use CLI, you can add and delete version branches with dedicated commands. Alternatively, you can create version branches during the file upload.
Read more about Branch Management with CLI.
Prioritizing Branches
You can set a specific priority for each branch by clicking an arrow icon next to the needed branch. Then translators will see branches sorted according to their priority on the language page and in the Editor.
Branches might have the following priorities:
– low
– normal
– high
To set a priority for your branches, follow these steps:
- Open your project and go to Content > Files.
- Click an arrow icon next to the needed branch to set the preferred priority.
Дублікати
Через те, що гілки є різними версіями одного продукту, зміст локалізації в них зазвичай дублюється. To help translators translate versions consistently and avoid additional translation costs, we have the Show within a version branch option that allows hiding duplicated strings only between versions. If your source files contain strings with apparent identifiers (keys), it’s better to use a strict version of this option. In other cases, feel free to use a regular one.
When this option is chosen, only the master strings first uploaded to the system should be translated. All duplicated strings will automatically gain the translations from the master strings. 
Запропонований робочий процес
To make sure versions work smoothly for your Crowdin project, we recommend the following workflow:
- Upload your project files to the Crowdin project using one of the methods available.
- Open your project and go to the Settings tab.
- Scroll down to the Translations > Duplicate Strings and choose the option recommended for versions.
На екрані нижче показано, як працює робочий процес на практиці. Усі тексти з гілок Master, Branch 1 і Branch 2 передається на сервер перекладу відразу після їх появи, навіть якщо гілки ще не об’єднані в цій гілці Master. 
Translation Download
Translations from all version branches are placed in one ZIP archive when downloaded through the web interface. Use the CLI or API to download the translations for each branch individually.
Translation Download using API
To download translations of the specified version branch with API, you can use the following API methods:
- Build Project Translation - make sure to use the CrowdinTranslationCreateProjectBuildForm schema
- Check Project Build Status
- Download Project Translations
Translation Download using CLI
Завантажити переклади з вказаної гілки версії:
$ crowdin download -b branch_name
Злиття гілок
Гілка Master буде містити нові тексти з гілок Feature як тільки вони поєднуються. While synchronizing with Crowdin, texts in the Master branch are populated with translations from the appropriate branch.
After synchronizing the updated Master branch with Crowdin, you can remove the Feature branch from Crowdin. Усі переклади зберігатимуться в цій гілці Master.
Підтвердження перекладу гілки
You can verify translations on production using only the Feature branch before changes are merged with your Master branch. Such test deploy gives you an option of quick revert to the original Master branch version if needed.
