Skip to content

Include base requirements in requirements-dev.txt#5064

Merged
sarthakag merged 2 commits into
GoogleCloudPlatform:developfrom
sarthakag:feature/update-test-dependencies
Mar 13, 2026
Merged

Include base requirements in requirements-dev.txt#5064
sarthakag merged 2 commits into
GoogleCloudPlatform:developfrom
sarthakag:feature/update-test-dependencies

Conversation

@sarthakag

Copy link
Copy Markdown
Contributor

To ensure a consistent and complete testing environment, it's ideal to include the runtime dependencies within the development dependencies.

Submission Checklist

NOTE: Community submissions can take up to 2 weeks to be reviewed.

Please take the following actions before submitting this pull request.

  • Fork your PR branch from the Toolkit "develop" branch (not main)
  • Test all changes with pre-commit in a local branch #
  • Confirm that "make tests" passes all tests
  • Add or modify unit tests to cover code changes
  • Ensure that unit test coverage remains above 80%
  • Update all applicable documentation
  • Follow Cluster Toolkit Contribution guidelines #

@sarthakag sarthakag requested review from a team and samskillman as code owners January 5, 2026 10:15
@sarthakag sarthakag added the release-chore To not include into release notes label Jan 5, 2026
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @sarthakag, 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 aims to enhance the consistency and completeness of the development and testing environment. By integrating the base runtime dependencies directly into the development requirements file, it ensures that all necessary packages are present, thereby preventing potential dependency-related issues and streamlining the setup process for developers.

Highlights

  • Development Environment Consistency: The requirements-dev.txt file now includes a reference to requirements.txt, ensuring that all runtime dependencies are automatically installed alongside development dependencies for a complete testing environment.

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

@sarthakag sarthakag enabled auto-merge January 5, 2026 10:16

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

Copy link
Copy Markdown
Contributor

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 intends to include base requirements within the development requirements, which is a commendable practice for ensuring a consistent environment. However, the referenced requirements.txt file contains several package versions that do not appear to be available on the public PyPI index. This will cause the development environment setup to fail. This critical issue needs to be resolved by correcting the versions in requirements.txt before this change can be merged.

@SwarnaBharathiMantena

SwarnaBharathiMantena commented Jan 7, 2026

Copy link
Copy Markdown
Contributor

If we are combining both, is there an intention to clean up this duplicate pip install?

pip install -r community/modules/scheduler/schedmd-slurm-gcp-v6-controller/modules/slurm_files/scripts/requirements.txt

@sarthakag sarthakag merged commit ad3511a into GoogleCloudPlatform:develop Mar 13, 2026
10 of 74 checks passed
@sarthakag sarthakag deleted the feature/update-test-dependencies branch April 17, 2026 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-chore To not include into release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants