Skip to content

chore!: enable --windows_enable_symlinks by default#3663

Open
rickeylev wants to merge 1 commit intobazel-contrib:mainfrom
rickeylev:chore.enable.windows.symlinks
Open

chore!: enable --windows_enable_symlinks by default#3663
rickeylev wants to merge 1 commit intobazel-contrib:mainfrom
rickeylev:chore.enable.windows.symlinks

Conversation

@rickeylev
Copy link
Collaborator

Supporting Windows without full symlink support is quite difficult because we rely on symlinks in many places. Since Windows support is mediocre already, just require symlinks to be enabled. Symlink support in Windows has been around for a long time now and is available via non-admin mechanisms such as DevMode.

Supporting Windows without full symlink support is quite difficult
because we rely on symlinks in many places. Since Windows support is
mediocre already, just require symlinks to be enabled. Symlink support
in Windows has been around for a long time now and is available via
non-admin mechanisms such as DevMode.
@rickeylev rickeylev requested a review from aignas as a code owner March 12, 2026 04:09
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 streamlines Bazel's operation on Windows by mandating full symlink support. By enabling the --windows_enable_symlinks flag by default, the project simplifies its codebase and development efforts, as symlinks are fundamental to various Bazel functionalities. This change removes the complexity of supporting environments with limited symlink capabilities, leading to a more consistent and robust experience for Windows users who have symlink support enabled.

Highlights

  • Default Symlink Requirement on Windows: The --windows_enable_symlinks flag is now enabled by default in .bazelrc for Windows users, making full symlink support a requirement due to its extensive use in Bazel's operations (runfiles, venvs). This change simplifies Windows support by removing the need to handle environments without full symlink capabilities.
  • Changelog Update for Breaking Change: The CHANGELOG.md has been updated to reflect this change as a breaking change, advising users to explicitly add startup --windows_enable_symlinks to their .bazelrc if they encounter issues, ensuring compatibility with the new default behavior.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • .bazelrc
    • Added a new startup flag startup --windows_enable_symlinks to enable full symlink support on Windows by default.
    • Included comments explaining the rationale behind requiring symlinks due to their extensive use in Bazel.
  • CHANGELOG.md
    • Introduced a new 'Breaking' change entry under the 'Changed' section.
    • Documented that --windows_enable_symlinks is now required and provided guidance for users to update their .bazelrc.
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.

@gemini-code-assist
Copy link
Contributor

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

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.

2 participants