-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create GitHub action to automatically update the emoji keywords functionality #542
Comments
@axif0, do you have interest in working on this? Making a few of the aspirational issues now :) |
Are we looking for the last releases of cldr-json for cldr-annotations-derived-full and cldr-annotations-full? Then like workflow checks the version if it is outdated then we can update our version? Or we periodically run the workflow and clone the repo and just updated our src/scribe_data/unicode. |
Would be kind of a combination of both options, @axif0 :) Similar to the Scribe Bot workflow, we'd check to see if there's a change and if there's a new update and if not then we cancel, but if there is then we update src/scribe_data/unicode with the new versions of these files 😊 |
Used DERIVED_LANGS, FULL_LANGS and to get the names of languages. By passing the language one by one in the githubusercontent -
Then we checked if downloaded |
Amazing progress on all of this, @axif0! 🚀 |
Terms
Description
As discussed in the issue planning meeting, a functionality that would be really nice to add in is a workflow that checks to see if there is new emoji data and then automatically sends a PR to update the data. Specifically we'd want the cldr-annotations-derived-full and cldr-annotations-full data that are found in src/scribe_data/unicode to be updated.
As a first step, we'd need to check around when this data is normally updated and then look into when to run the action 😊
Contribution
@axif0 could work on this as a part of Outreachy 😊
The text was updated successfully, but these errors were encountered: