Automation and branches- Using YAMLFish to easily manage I18n translations in your project

In the last article, we've discovered the basics of

From the YAMLFish dashboard, they will be able to see translation keys specific to the branch, and update the value for their locale.

Fetching the new translations

Once the translators have finished filling the keys, we can now move forward.

The first thing we need to do is merge our branch, so that our CI/CD pipeline will run and push the new translations for our en🇬🇧 locale.

Once they are pushed, we can go on the YAMLFish dashboard and merge our branch :

We only want to merge our secondary locales as our main locale has been updated already.

Once this is done, we can simply pull our new translations :

yamlfish pull fr

yamlfish pull es

This will update our fr.yml and es.yml files (in config/locales by default) with the new translations.

We can now commit the changes, and deploy our new feature !

Conclusion

Thanks to YAMLFish we were easily able to have our new feature translated by non-dev people in a frictionless way, from the comfort of our CLI.

In the next article, we'll see how to manage cases when non-dev people want to update translations in the main locale.