The only thing that is needed is that the API is connected to the GitHub repository. The goal is that the API communication is automated between the main repo and the Crowdin project. So if I make an update on the Crowdin project it should make a direct PR commit to the Andorid/core strings. Ideally this will eliminate most manual work from the dev side.
Description
Hey all,
We are finally into a position where we can start a full migration of our strings from Transifex to Crowdin.
In Crowdin the project that we would like to migrate to is here: https://brave-software.crowdin.com/u/projects/6
The API documentation can be found here: https://support.crowdin.com/developer/api/v2/
The only thing that is needed is that the API is connected to the GitHub repository. The goal is that the API communication is automated between the main repo and the Crowdin project. So if I make an update on the Crowdin project it should make a direct PR commit to the Andorid/core strings. Ideally this will eliminate most manual work from the dev side.
Let me know if you have any questions
Steps to reproduce
n/a
Actual result
n/a
Expected result
n/a
Reproduces how often
Easily reproduced
Desktop Brave version (brave://version info)
n/a
Android device
n/a
Channel information
Reproducibility
Miscellaneous information
No response