I think there should be more options available here as an org has to wait for their language to be 100% translated/reviewed in order to get those strings via automated commit.
What if I want to pull translations weekly from my Transifex irrespective of the fact that language is fully reviewed or not?
So, this new integration is good for those orgs starting up new on transifex or those who are just about to hit that 100% mark to utilize this feature regularly but those org/ users which have reviewed/translated percentage of language as 20-30% they can’t use this for now.
I can see why it is not very clear from the attached screenshot, but pushing content is per resource per language, and not just per language. For example, if I have a resource whose translation reaches 100% in Spanish, content will be pushed, regardless if the Spanish language is 100% for all available resources or not.
The reason for this, is that internally the Github integration uses Transifex’s own webhook system, which happens on a resource level. This is not a hard requirement though, so if this is a recurring request, we can further tune it (to a weekly base like you said, for example).
Actually, we recently performed merging of multiple translation files into one as multiple file approach was confusing to contributors. Maybe we’ll switch to that in future again.
And, yes, we would be happy to see the weekly pull option implemented if other users/orgs also feel the requirement.
Weekly pull will definitely be very important for FLOSS projects where volunteer translators sometimes only have time to translate a subset of the project.
We released an option that can help you syncing translations to GitHub on less than 100% translated resources. At the moment this is not automated, like you suggest here, but it’s a step one on the direction in discussion, manual sync.
We would appreciate any feedback, input and ideas that can make the integration more useful.
