-
Notifications
You must be signed in to change notification settings - Fork 27
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
fix(theme-stackoverflow): add missing empty space after "position" on… #145
Conversation
🦋 Changeset detectedLatest commit: 519b1d8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
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 |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThe changes introduce a patch to the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yaml
is excluded by!**/pnpm-lock.yaml
Files selected for processing (1)
- themes/stackoverflow/style.css (1 hunks)
Files skipped from review due to trivial changes (1)
- themes/stackoverflow/style.css
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.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yaml
is excluded by!**/pnpm-lock.yaml
Files selected for processing (3)
- apps/registry/package.json (1 hunks)
- packages/eslint-config-custom/package.json (1 hunks)
- themes/stackoverflow/package.json (2 hunks)
Files skipped from review due to trivial changes (1)
- apps/registry/package.json
Additional comments not posted (3)
packages/eslint-config-custom/package.json (1)
9-9
: Approve the dependency update but verify compatibility.The update from
"eslint-config-turbo": "^1"
to"eslint-config-turbo": "^2"
is approved. However, it's crucial to ensure that this major version update is compatible with the rest of the project's ESLint configuration.Run the following script to check for ESLint configuration files that might need updates:
themes/stackoverflow/package.json (2)
46-52
: Approve the Storybook and i18next updates but verify compatibility.The updates to Storybook packages and
storybook-react-i18next
from^2.0.1
to^3
are approved. However, it's crucial to ensure that these updates are compatible with the existing project setup and do not introduce any breaking changes.Run the following script to check for Storybook configuration files that might need updates:
Also applies to: 68-69
45-45
: Approve the ESLint dependency change but verify linting rules.The replacement of
@repo/eslint-config-custom
with a direct dependency oneslint
is approved. However, verify that the linting rules and configurations are correctly updated to reflect this change.Run the following script to check for ESLint rule files that might need updates:
Also applies to: 65-65
Closes #155 |
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.
lgtm
I do not remember how this will be released. Are there docs on the process? |
The registry is importing stackoverflow theme from the workspace, so after it is merged, vercel will just build and deploy the registry which will use the latest/relative files of the theme. But you could also bump the minor in the stackoverflow theme and npm publish (unless you have an action for it already, which you may have did) |
Lets hold on to this for a moment and add a changeset. This could trigger the release, will double check. |
I just pushed something straight to master, I will go back to putting up PR's |
I added the changeset which should trigger the release flow once this PR is merged by opening a release PR. However the PR here cannot be merged because you disabled the test script and it is still required status check. Do you want to bring back the test script or do you want to remove it as a required check? |
@@ -6,7 +6,7 @@ | |||
"license": "MIT", | |||
"dependencies": { | |||
"eslint-config-prettier": "^8.3.0", | |||
"eslint-config-turbo": "^1", | |||
"eslint-config-turbo": "^2", |
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.
Not sure about this one. Should probably not be part of the PR.
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.
Seems to be important. Idk why. Maybe because the turbo version got updated or so.
I'm on for a couple hours tonight, happy to bring back the |
IIRC it used to work for a while until certain changes were made to the codebase. If after such changes a |
… print outs
Before:
After:
Summary by CodeRabbit
Summary by CodeRabbit
jsonresume-theme-tailwind
to link it to the workspace.