There is actually a bug related to this. So I’ve noticed that if you pre-translate a string using AI and then try to upload the same translation, it won’t get to TM. But if you skip the pre-translation step and just upload directly, it will get there.
It creates an incosistency bug that if uploaded message is the same as pre-translated one, Crowdin just ignores it and thus does not add it to TM, while if it’s new, it is added.
In this case I can’t just approve it, because approval should be done by a proofreader.
Adding an option to add uploaded via CLI translation to TM will sove both of the problems and I believe adding it won’t be too difficult, as you already have such option in the UI.
