Skip to content

fix sparse checkout #7007#7012

Merged
waruqi merged 3 commits intodevfrom
git
Nov 10, 2025
Merged

fix sparse checkout #7007#7012
waruqi merged 3 commits intodevfrom
git

Conversation

@waruqi
Copy link
Member

@waruqi waruqi commented Nov 10, 2025

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @waruqi, 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 addresses an issue related to sparse checkout functionality, specifically when combined with shallow cloning by tag. It introduces logic to correctly prioritize sparse checkout patterns, preventing potential conflicts and ensuring that the intended files are checked out. The changes lead to more robust and predictable behavior for package downloads within the system.

Highlights

  • Improved Sparse Checkout Logic: The pull request refactors the handling of url_includes (sparse checkout patterns) to prevent conflicts with shallow cloning when a tag is specified, ensuring that sparse checkout takes precedence.
  • Consistent Submodule Handling: The condition for updating submodules has been updated to consistently use the clone_submodules variable, improving code clarity and maintainability.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@waruqi waruqi added this to the v3.0.5 milestone Nov 10, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request addresses an issue with sparse checkouts, specifically when a tag is involved. The changes in download.lua correctly modify the logic to avoid a shallow clone when url_includes is present, ensuring the sparse checkout process is used instead. The introduction of local variables for sparse_includes and clone_submodules is a good refactoring that improves readability. I have one suggestion to further enhance code maintainability by removing a duplicated variable definition.

@waruqi waruqi merged commit ed81f6d into dev Nov 10, 2025
43 of 44 checks passed
@waruqi waruqi deleted the git branch November 10, 2025 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant