quick question: I’m using the Gitlab integration and wanted to rename the Gitlab branch we connected a large project to, because it may be mistaken for a feature branch otherwise.
Would that cause any issues with the integration? Just checking before I go ahead. Thanks!
Hi!
It shouldn’t create any issues. You can enable the duplicate option in the Project settings > Import tab to Show within a version branch (regular detection)
After you edit the branch name and integration will sync, all translations will move from the old branch to the newly uploaded to the project. It might take some time (not immediately), if there are lots of translations in the project
After you verified that all translations are moved to the new branch feel free to delete the old branch from the Sources tab (branch won’t be deleted automatically after the sync)
We just renamed our github branch and all the approval in crowded was gone, etc. my question is that can you point me any docs that describe how to do it?
Hi @toyip-fadv
Unfortunately, we don’t have documentation on the matter. You can mass approve translations in the Side-by-Side Editor view select all strings > tick button to approve all, check the screenshot below:
Yes, if it’s a branch/folder in Crowdin and it is just renamed. But if it’s something that comes from outside, like Github, in most cases it’s not just renamed, but merged with another branch, and then renamed, so this may cause the progress lost.
When a GitHub branch is renamed, it can disrupt the link with the translations as the system treats it as a new branch. To prevent losing progress in the future, it’s best to avoid renaming branches that are actively being used for translations.
If you need to rename a branch for some reason, you could first duplicate the branch within Crowdin to preserve the translations and then proceed with the renaming in GitHub.
For now, to recover your progress, you can run TM pre-translation with the “Approved added suggestions” option turned on. If the translations were committed to the repository before the branch was renamed, you should also be able to restore them from your version control system (and after that you can “approve all” in bulk using Crowdin Editor).