-
Notifications
You must be signed in to change notification settings - Fork 142
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
feat(attributes): use frequency alongside isCommon #576
Conversation
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.
really good stuff! super close
@Effiti LGTM just to confirm, did you run this migration locally to see if it works as expected? |
@Effiti you don't need to run docker! you can just follow the testing portion of the README |
|
@Effiti it seems like our pipeline is blocked by a weird yarn error! I've commented on the related thread to see if there's any solution to the bug: yarnpkg/yarn#8580 (comment) If we don't hear back soon (by Wednesday at the very latest), I'll consider switching from yarn to npm so we can unblock deploys |
@Effiti it looks like our README didn't walk through an extra necessary step to contribute (apologies!) here's the guide |
@ijemmao do I have to close and reopen the PR? I followed the instructions but the CI is still not working. Here is a screenshot of the settings page: |
@Effiti hmm yeah this is odd :/ i did find this thread that could be related: https://github.com/orgs/community/discussions/26283 (thanks for your patience, i'm gonna fork my own repository to make a change to see if i can fix the bug locally) |
I set up ssh authentication for git on my machine (i think that's what the discussion was referring to), even though I already had GPG-Signing set up for git before. I'm just gonna keep fixing minor issues in the README in order to trigger the CI until the issue is resolved 😄. |
this can be the first step in an effort towards deprecating isCommon