-
Notifications
You must be signed in to change notification settings - Fork 0
chore: willboosterify this repo #551
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
Conversation
Summary of ChangesHello @exKAZUu, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request performs a 'willboosterification' of the repository, focusing on standardizing development practices and updating project dependencies. It refines internal commit guidelines, configures Yarn to pre-approve key Next.js and React packages, and systematically updates a wide array of npm dependencies to their latest compatible versions. The overall aim is to align the repository with current best practices and ensure a robust, up-to-date development environment. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
このプルリクエストは、リポジトリを "WillBooster" の標準に合わせるための依存関係の更新とドキュメントの修正を含んでいます。全体的に、設定やドキュメントが改善されています。
yarn.lock ファイルにおいて、react と react-dom のバージョンが複数(19.2.0 と 19.2.1)混在してしまっている問題点を指摘しました。これにより、予期せぬ動作やバンドルサイズの増加につながる可能性があるため、package.json の resolutions フィールドでバージョンを統一することを推奨します。
リポジトリのスタイルガイドに従い、レビューは日本語で行いました。
| "react-dom@npm:^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0": | ||
| version: 19.2.1 | ||
| resolution: "react-dom@npm:19.2.1" | ||
| dependencies: | ||
| scheduler: "npm:^0.27.0" | ||
| peerDependencies: | ||
| react: ^19.2.1 | ||
| checksum: 10c0/e56b6b3d72314df580ca800b70a69a21c6372703c8f45d9b5451ca6519faefb2496d76ffa9c5adb94136d2bbf2fd303d0dfc208a2cd77ede3132877471af9470 | ||
| languageName: node | ||
| linkType: hard |
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.
react-dom のバージョンが複数(19.2.0 と 19.2.1)混在する状態になっています。この変更により、@storybook/addon-docs などが依存する react-dom が 19.2.1 に解決されるようになり、プロジェクトで直接使用されている 19.2.0 との重複が発生しています。
これにより、予期せぬ動作やバンドルサイズの増加を引き起こす可能性があります。
package.json の resolutions フィールドを使用して、バージョンを一つに統一することを強く推奨します。例えば、すべての react-dom を 19.2.1 に統一するには、以下のように設定します。
"resolutions": {
"react-dom": "19.2.1"
}その後 yarn install を実行してください。
| "react@npm:^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0": | ||
| version: 19.2.1 | ||
| resolution: "react@npm:19.2.1" | ||
| checksum: 10c0/2b5eaf407abb3db84090434c20d6c5a8e447ab7abcd8fe9eaf1ddc299babcf31284ee9db7ea5671d21c85ac5298bd632fa1a7da1ed78d5b368a537f5e1cd5d62 | ||
| languageName: node | ||
| linkType: hard |
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.
react のバージョンが複数(19.2.0 と 19.2.1)混在する状態になっています。この変更により、@storybook/addon-docs などが依存する react が 19.2.1 に解決されるようになり、プロジェクトで直接使用されている 19.2.0 との重複が発生しています。
これにより、予期せぬ動作やバンドルサイズの増加を引き起こす可能性があります。
package.json の resolutions フィールドを使用して、バージョンを一つに統一することを強く推奨します。例えば、すべての react を 19.2.1 に統一するには、以下のように設定します。
"resolutions": {
"react": "19.2.1"
}その後 yarn install を実行してください。
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.
Pull request overview
This PR performs a "willboosterify" chore that standardizes the repository's configuration and updates dependencies. The main purpose is to align the codebase with WillBooster's standard practices, including dependency management and AI agent interaction guidelines.
- Updated Express from 4.21.2 to 4.22.1 and related dependencies with tilde version ranges for better flexibility
- Updated React and React DOM to include 19.2.1 alongside 19.2.0 to support different peer dependency requirements
- Clarified AI agent instructions to emphasize committing to "non-main branch" rather than "current branch"
- Added next, @next/*, react, and react-dom to the npm pre-approved packages list
Reviewed changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| yarn.lock | Updated Express to 4.22.1, React/React-DOM to include 19.2.1, and consolidated various dependency entries with tilde version ranges |
| GEMINI.md | Clarified commit instructions to specify "non-main branch" instead of "current branch" |
| CLAUDE.md | Clarified commit instructions to specify "non-main branch" instead of "current branch" |
| AGENTS.md | Clarified commit instructions to specify "non-main branch" instead of "current branch" |
| .cursor/rules/general.mdc | Clarified commit instructions to specify "non-main branch" instead of "current branch" |
| .yarnrc.yml | Added next, @next/*, react, and react-dom to npmPreapprovedPackages whitelist |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
No description provided.