-
Notifications
You must be signed in to change notification settings - Fork 43
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
Publish new functional color system #224
Conversation
🦋 Changeset detectedLatest commit: e3cd86e The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/primer/primitives/FiLh2apndXtKZVug9A5hi7Yk9w47 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we wait with merging this until users won't be able to disable the "Dark High Contrast" feature preview?
@simurai Yeah, let's hold off until we remove the feature flag from github.com. In the meantime, we'll need to keep this branch up-to-date if we make bug fixes. |
- name: Compute variable count | ||
run: npx ts-node .github/v2-var-count.ts | ||
env: | ||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The variables in colors/
and colors_v2/
are the same now so this action won't give us useful information anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks pretty straight forward, had a question but not sure if I am asking something that's out of step with the plan.
@@ -1,86 +0,0 @@ | |||
import {merge} from '../../src/utils' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this deletion count as major? Or was the direct data/colors/dark_dimmed
never used by external users?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These source files are never referenced directly so it has no impact on consumers.
"introShelf.gradientRight": "success.subtle", | ||
"introShelf.gradientIn": "canvas.default", | ||
"introShelf.gradientOut": null | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a side thought, it would be awesome to automate this script and have actions check it in on prs. So nobody will have to remember to re-run the script.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I thought about that too. But I'm curious if that's something we always want to automate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's see how the manually keep the file up-to-date goes after the v2 migration, then we can re-evaluate.
Summary
For the past few months, we've been testing new color variables (stored in the
colors_v2
directory) on github.com. We're now ready to add the new color variables to thecolors
directory and deprecate old color variables.This PR does the following:
Note: We should not release this change until we've updated our color system docs (#225)