Open brandones opened 3 years ago
The problem was that tx init
was overwriting the already-existing .tx/config
file. Of course, tx pull
should give some kind of useful output about the configuration in this case.
For the edification of future generations, this is the working workflow configuration:
name: Update translation files from Transifex
on:
schedule:
- cron: '36 0 * * *'
workflow_dispatch:
jobs:
build:
runs-on: ubuntu-latest
env:
TX_TOKEN: ${{ secrets.TRANSIFEX_API_KEY }}
steps:
- uses: actions/checkout@v2
- uses: actions/setup-python@v2
- run: python -m pip install --upgrade pip
- run: pip install transifex-client
- run: tx pull -a --minimum-perc=1 --traceback
- uses: EndBug/add-and-commit@v7
with:
add: app/js/translations
message: 'Update translations'
Hello,
Glad you figured it out. There is always room for improvement, so we will check out what you said.
However, we are also working on a new version of the TX client, which can be found here... https://github.com/transifex/cli. It is still considered an alpha version, but it is fairly stable, and it also uses the new version of the API (v3).
Let us know if you need anything else!
Regards, Ryan Transifex Support
I'm trying to set up a GitHub Action which uses
tx pull
to update translations. Here is the action:I'm testing it out using Act. I'm seeing the following output for the
tx
parts:So
tx pull
is evidently not actually doing anything, but neither is it offering any information that could be used to debug, even with both--debug
and--traceback
provided. It's even exiting with status code 0. This leaves me at a total impasse.