build: Enable incompatible_no_implicit_file_export in bazelrc

[hofbi]

Identified by bazelbuild/bazel#27674 (comment), I want to see what else fails when flipping this flag on top of #3471.

[gemini-code-assist]

Summary of Changes

Hello @hofbi, I'm Gemini Code Assist¹! 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 enables the incompatible_no_implicit_file_export flag within the .bazelrc configuration. The objective is to proactively test the build system's compatibility with this new Bazel behavior, allowing for early detection and resolution of any issues that may arise from its activation.

Highlights

• Bazel Flag Enablement: The incompatible_no_implicit_file_export flag has been enabled in the .bazelrc file.
• Compatibility Testing: This change is intended to identify further build failures or regressions when this specific incompatibility flag is active, following up on previous related work.

🧠 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.

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]

Code Review

This pull request enables the incompatible_no_implicit_file_export flag in .bazelrc. This is a valuable change that will help enforce stricter dependency management by requiring explicit file exports. The change is correctly implemented by adding the flag to the common configuration, which will apply it to all Bazel commands. This will help identify and fix areas in the codebase that rely on the legacy implicit export behavior, improving overall build hygiene. The change looks good to me.

[rickeylev]

@hofbi I updated this to head after the fix to expose runtime_env_interpreter.sh. CI shows some new additional visibility errors

[hofbi]

Thank you! I will continue with this in January.