You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have an already existing translation file in your repo, and then you push a commit to add that to transifex by adding it in .tx/config, txgh will not push that resource to transifex because the github webhook does not have the translation file as part of the added/modified files.
Is this something that sounds worth supporting? The easiest way to do this would be to re-sync every resource. Otherwise you would have to diff the .tx/config against the last version of it to see which resources were actually added.
The text was updated successfully, but these errors were encountered:
Yeah, unfortunately that's a use case txgh doesn't support super well. All we'd really have to do is listen for changes to .tx/config in addition to files that match the file_filters. I think I filed an issue for that internally, but never got around to implementing it.
I did however write a couple of scripts for us internally to do this. I had originally wanted to create a txgh CLI client, but it was pretty low priority. This script uploads all resources for the master branch and this script validates your setup is correct. Obviously these are tailored for our needs and some work would need to be done to make them applicable to a wider user base, but maybe they'll work for you :)
If you have an already existing translation file in your repo, and then you push a commit to add that to transifex by adding it in
.tx/config
, txgh will not push that resource to transifex because the github webhook does not have the translation file as part of the added/modified files.Is this something that sounds worth supporting? The easiest way to do this would be to re-sync every resource. Otherwise you would have to diff the
.tx/config
against the last version of it to see which resources were actually added.The text was updated successfully, but these errors were encountered: