Hello,
We are managing a large Android project with multiple feature branches running in parallel. We are using the modern smartling-cli and have hit a point of friction regarding the "intended" workflow for retrieving translations in a branched environment.
We use the following command to push strings from our feature branches:
smartling-cli files push "path/to/strings.xml" \
--type android \
--job "Feature-Name" \
--branch "@auto" \
--authorize
This works perfectly. The @auto flag correctly prefixes the File URI in the Smartling dashboard with our Git branch name (e.g., feature-login/path/to/strings.xml), preventing collisions between developers.
When it comes time to pull those translations back into the specific feature branch, there is no corresponding --branch "@auto" flag for the pull command.
What is the recommended "Golden Path" for pulling translations pushed with --branch?
Thanks
Hello,
We are managing a large Android project with multiple feature branches running in parallel. We are using the modern smartling-cli and have hit a point of friction regarding the "intended" workflow for retrieving translations in a branched environment.
We use the following command to push strings from our feature branches:
This works perfectly. The @auto flag correctly prefixes the File URI in the Smartling dashboard with our Git branch name (e.g., feature-login/path/to/strings.xml), preventing collisions between developers.
When it comes time to pull those translations back into the specific feature branch, there is no corresponding --branch "@auto" flag for the pull command.
What is the recommended "Golden Path" for pulling translations pushed with --branch?
Thanks