add github action of transifex upload

[unkcpz]

Migrate transifex integration from travis.ci to github action. @csadorf

I am not sure whether TRANSIFEX_USER and TRANSIFEX_PASSWORD set previously still available. You may need to set them if not.

[codecov]

Codecov Report

Merging #3958 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #3958   +/-   ##
========================================
  Coverage    78.31%   78.31%           
========================================
  Files          461      461           
  Lines        34076    34076           
========================================
  Hits         26687    26687           
  Misses        7389     7389           

Flag	Coverage Δ
#django	70.36% <ø> (ø)
#sqlalchemy	71.21% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e8e7e46...341327e. Read the comment docs.

[csadorf]

This looks fine to me. I just have two requests to add some comments to provide a little bit more context.

[unkcpz]

There seems no way to manually trigger the action. So have to wait until next release to make sure this workflow is working properly. 🤞

I trigger it in a hack way and it failed, maybe since the secret keys are not set.

[unkcpz]

I recall that the TRANSIFEX_USER shall be set as api and TRANSIFEX_PASSWORD is the token generated from transifex. fyi, https://docs.transifex.com/api/introduction#authentication

And API token: https://www.transifex.com/user/settings/api/

As a reference, the context of my transifexrc file is:

[https://www.transifex.com]
api_hostname = https://api.transifex.com
hostname = https://www.transifex.com
password = **** [redacted]
username = api

Edit: I redacted the password. csa

[csadorf]

I recall that the TRANSIFEX_USER shall be set as api and TRANSIFEX_PASSWORD is the token generated from transifex. fyi, https://docs.transifex.com/api/introduction#authentication

And API token: https://www.transifex.com/user/settings/api/

As a reference, the context of my transifexrc file is:

[https://www.transifex.com]
api_hostname = https://api.transifex.com
hostname = https://www.transifex.com
password = ****
username = api

@unkcpz Did you post the actual credentials? In this case, please reset this password immediately and send the new password to my personal email. Thank you.

Edit: In either case, please send the actual credentials to my personal email, thank you.

[unkcpz]

@csadorf no is just a example, I don't have the privilege to log in aiida account in transifex. @ltalirz has the actual credentials.

[csadorf]

I trigger it in a hack way and it failed, maybe since the secret keys are not set.

@unkcpz It might be a good idea for us to debug this workflow before we merge it by simply running it temporarily on push. It would only be executed for this branch in this case. We would then remove that trigger prior to merge after we have verified that it works. What do you think?

@ltalirz Can you verify that the secrets have been added to the repository?

[ltalirz]

Sorry guys, I've added them now (user: api, password: the api token).
Please try again

[csadorf]

Please try to run the workflow on push and then re-request review. Thx!

[unkcpz]

It is strange. I can successfully upload the pot to my account check here (and the workflow file with only project name different), but with all similar processes, still failed when setting and uploading to aiida account.

I got: tx ERROR: EOF when reading a line . This is most likely caused by incorrectly setting configuration file.

@ltalirz Can you reconfirm you add and set secrets:

TRANSIFEX_PASSWORD -> token from transifex
TRANSIFEX_USER -> api

Thanks!

[ltalirz]

Hi @unkcpz , sorry about this, I believe the token I had stored was missing a few characters.
I've generated a new one and updated the github secrets.

I've also changed your status in the aiida docs to project maintainer in case it is useful at any point.

[unkcpz]

emmm... unfortunately, same error here.

Maybe, it is not allowed to using secrets keys in pull request actions? It cause anyone can access and use the secret token by just making a pull request, which is unsafe. In this case, could you help to make a push for test?

I've also changed your status in the aiida docs to project maintainer in case it is useful at any point.

Thanks! 😄

[csadorf]

Maybe, it is not allowed to using secrets keys in pull request actions? It cause anyone can access and use the secret token by just making a pull request, which is unsafe. In this case, could you help to make a push for test?

Ah sorry that I missed that. The secret is indeed not available for pull requests. We will need to push directly to the repository. I'll do that.

[csadorf]

@unkcpz Just pushed to ci-test-transifex-action branch, action running here: https://github.com/aiidateam/aiida-core/actions/runs/86005424

[ltalirz]

Seems to have worked, right?

[unkcpz]

It works now. Cheers! And change trigger event back to release, ready to be merged.

Thank you guys! 😃

[unkcpz]

However, I concerned if release event can successfully run the action as push? I didn't find information about which event is able to use secrets. @csadorf

[csadorf]

However, I concerned if release event can successfully run the action as push? I didn't find information about which event is able to use secrets. @csadorf

The release event is going to trigger the workflow with the appropriate permissions. So don't worry about that.