...
signatureName: A signature included with commits. If not specified then connector uses “Wordbee”
signatureEmail: The email included with commits. If not specified then connector uses “noreply@wordbee.com”
To translate additional branches in the repository, then activate the “multi-branch” properties in the next chapter:
multibranch: { … } See next chapter
Each Beebox project can have its own configuration.
Configure localization of multiple branches
With this feature you can localize (inside a single Beebox project) any number of branches in your repository. For example, any changes to translatable files in all your feature branches or all your release branches.
Simply add to your configuration a node similar to this:
| Code Block |
|---|
...
"multibranch": {
"enabled": true,
"staticBranches": [
"master",
"develop",
"release"
],
"regexBranches": [
"^feature.+"
]
} |
enabled: Set to true to activate this feature.
staticBranches: A list of branch names to localize. You should include here the branch name you set on the branch property.
regexBranches: A list of regular expressions to dynamically capture branch names such as all branches prefixed with “feature/”.
How does it work?
With each “Auto run”, Beebox will first fetch the latest list of branches and clone any new branches to its “in” directory.
It will then pull changes from all listed branches. Note that all branches are cloned to the “in” directory and to subdirectories according to the branch names.
Pulled changes trigger translation workflows as any Beebox project would do with new or changed files showing up in the “in” directory.
Any finished translations (see below how to automatically transfer and rename in the “in” directory) will be pushed and committed to the respective target branch.
The commit history and the Beebox logs show each individual action.
Configure location of translated files
...