-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Update development.md to clarify bootstrap instructions #2684
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
base: master
Are you sure you want to change the base?
Conversation
📝 WalkthroughWalkthroughA clarification was added to the documentation, specifying that installing development dependencies and fetching the latest translations should be performed inside the development container when using one for development. Changes
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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
🧹 Nitpick comments (1)
docs/frontend/development.md (1)
145-147
: Refine or merge environment notes for clarityThe new note is helpful, but two consecutive
:::note
blocks can be confusing. Consider merging this with the previous note and updating the wording to improve readability and grammar. For example::::note These commands must be run manually, even if you are using dev containers. If you are developing inside a dev container, run them **inside the container** to ensure the paths and mounts resolve correctly. :::Also, add “the” before “dev container” in the sentence for grammatical correctness.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting
📒 Files selected for processing (1)
docs/frontend/development.md
(1 hunks)
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
Clarify the instructions for fetching translations when working inside a development container.
- Added a note emphasizing that
script/setup_translations
must be run inside the dev container. - Improved visibility of container-specific instructions in the frontend development guide.
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 clarifies that the translation setup step must be run inside a development container.
- Adds a note indicating the
script/setup_translations
command should be executed within the dev container. - Emphasizes manual execution even when using dev containers.
Should I do something else to get a review? |
Proposed change
Clarify the instructions for bootstrapping the development environment because I spent 20 minutes trying to figure out how to run bootstrap scripts on Windows.
Type of change
Checklist
Additional information
Summary by CodeRabbit