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
Set up a periodic GitHub Action (e.g., weekly) to run this script so new translators are added periodically (I'm assuming there is already something like this for the other teams)
In order to get the information from the Crowdin's API we need an API token with the right permissions. An idea could be to create an API token per organization and add it as a secret so it can be retrieved as an environment variable. Let me know what you folks think and I can start working on a PR to do this integration.
The text was updated successfully, but these errors were encountered:
Currently, there is no automated way to retrieve the usernames of Crowdin translators contributing to numpy.org and add them to the appropriate teams.
For solving this I propose creating a script with the following functionality:
Use the Crowdin's (/projects/{project_id}/members) endpoint to fetch project members. In out case it looks something like this:
Create a
.toml
file with the information retrieved matching the format of: https://github.com/numpy/numpy.org/blob/main/content/en/teams/translations-team.tomlSet up a periodic GitHub Action (e.g., weekly) to run this script so new translators are added periodically (I'm assuming there is already something like this for the other teams)
In order to get the information from the Crowdin's API we need an API token with the right permissions. An idea could be to create an API token per organization and add it as a secret so it can be retrieved as an environment variable. Let me know what you folks think and I can start working on a PR to do this integration.
The text was updated successfully, but these errors were encountered: