ci: automate lexicons updates #36
Open
+5,966
−5,836
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for tsky canceled.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR allows automating to update lexicons file to the latest state as I noticed the current file is a bit outdated because Bluesky recently added trending tags etc. and updated lexicons as well.
I wrote a new script
check-version-change.ts, which checks whether the generated lexicons are updated or not.A new workflow
update-lexicons.ymlruns that script and if the lexicon has a new version, it pushes a new commit.To determine if the lexicons need to be updated, I used this
Source:line (main...shuuji3:tsky:automate-lexicons-updates#diff-4fd548033d0c577f7362cbc14137a37e4c99f9df670040826c67db41998f70a9R10). When Bluesky published the new lexicons, the commit hash is updated here.