Migrate files to resource or references folder.#19503
Conversation
|
Hi @g-samroberts, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this. We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines. Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed. Thank you for your understanding and for being a part of our community! |
Summary of ChangesHello @g-samroberts, 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 focuses on a significant refactoring of the documentation structure by moving various files into dedicated Highlights
Changelog
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.
Code Review
This pull request primarily involves reorganizing documentation files by moving them into new resources and reference directories. The changes are extensive, covering numerous markdown files, documentation generation scripts, and the website's sidebar configuration to update links and paths according to the new structure. Overall, the refactoring is well-executed, but I found one instance of a broken link that needs to be corrected.
|
Build failed: Build process failed with link errors: |
|
Size Change: -2 B (0%) Total Size: 24.5 MB ℹ️ View Unchanged
|
jkcinouye
left a comment
There was a problem hiding this comment.
LGTM. I didn't manually check all the links - just read through them - since linting caught errors.
Summary
Migrate files to resource or references folder. Update existing links.
Related to #19359
Details
This is step two in unblocking multisidebar for the website. Putting these files into the correct folders allows us to make sure we can group reference and resource files by folder in the top nav.
Pre-Merge Checklist