Automatically update palette system data #230
Draft
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
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 adds a CI action that periodically runs the script that grabs Tumblr's built-in palette colors and creates a PR if they've been changed.
This was mostly just made because I was curious if Puppeteer needed special config to run in Linux CI environments if you had it control Firefox (answer: not really!) and this was the easiest way to satisfy that curiosity. Tumblr's palettes change infrequently enough that this seems kind of pointless, and I have to admit this is all a bit janky—the chance that something changes in Tumblr that breaks the automation before we actually get another Tumblr palette color change feels definitely-not-zero.
Kind of fun though.