automate component list#97
Open
dblatcher wants to merge 4 commits into
Open
Conversation
dblatcher
added
the
maintenance
Dependency Compatibility Matrix
|
oliverabrahams
approved these changes
May 11, 2026
oliverabrahams
left a comment
oliverabrahams
left a comment
Contributor
There was a problem hiding this comment.
Looks like a good improvement to me
This file contains hidden or 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
2 participants
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.
What does this change?
changes config.js to import the list of components to build styles for from a json file.
updates the create-component script to add the new name to the json file when creating the new component.
Adds a checklist markdown file summarising the steps to getting the component published.
How has this change been tested?
Ran the script locally
build-styled still works
How can we measure success?
slightly easier workflow for new components
Have we considered potential risks?
Should be technically safe - but worth considering if this is actually a better workflow.