[REFACTOR][CI] Clean up GitHub Actions platform build workflow and standardizing Python management with uv

[mshr-h]

This PR simplifies the GitHub Actions build/test workflow for platform CI (macOS + Windows) by consolidating duplicated jobs and standardizing Python environment management with uv.

[gemini-code-assist]

Summary of Changes

Hello @mshr-h, 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 refactors the GitHub Actions CI workflow for macOS and Windows platforms. The changes aim to simplify the build and test process by eliminating redundant job configurations and adopting uv for Python environment management, thereby improving the efficiency and maintainability of the CI pipeline.

Highlights

• CI Workflow Simplification: Consolidated duplicated jobs within the GitHub Actions workflow for macOS and Windows platform builds, reducing redundancy.
• Python Environment Management: Standardized Python environment management by replacing the previous conda setup with uv, streamlining dependency handling.

🧠 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

• .github/actions/setup/action.yml
  • Removed the composite action for setting up the Python environment using conda.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/main.yml

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 is part of a refactoring effort to clean up the GitHub Actions CI workflow. The main change in this patch is the removal of the .github/actions/setup/action.yml composite action, which was used for setting up a Conda-based Python environment. According to the PR description, this is being replaced by a standardized approach using uv. This change aligns with the goal of simplifying and modernizing the CI pipeline. As this is a file deletion, there are no specific code issues to address within this patch, assuming the dependent workflows are updated accordingly as part of the full pull request.