Skip to content

Revert "Use GitHub workflow to update MODULE.bazel.lock files."#1735

Open
phst wants to merge 1 commit intomasterfrom
nomerge
Open

Revert "Use GitHub workflow to update MODULE.bazel.lock files."#1735
phst wants to merge 1 commit intomasterfrom
nomerge

Conversation

@phst
Copy link
Owner

@phst phst commented Feb 23, 2026

This reverts commit abdf4ec.

We haven't needed this in a while, so remove it for now to remove some complexity.

This reverts commit abdf4ec.

We haven't needed this in a while, so remove it for now
to remove some complexity.
@gemini-code-assist
Copy link

Summary of Changes

Hello @phst, 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 reverts a previous commit that implemented a GitHub workflow to manage MODULE.bazel.lock files. The decision to remove this mechanism stems from its current lack of necessity, aiming to streamline the repository by eliminating unneeded complexity and maintenance overhead.

Highlights

  • Reverted Lockfile Update Mechanism: The pull request reverts commit abdf4ec, which introduced a GitHub workflow-based script for updating MODULE.bazel.lock files.
  • Reduced Repository Complexity: The script update_lockfiles is removed as it is no longer needed, thereby simplifying the repository's maintenance and reducing unnecessary complexity.

🧠 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
  • update_lockfiles
    • Removed the script responsible for orchestrating GitHub workflow runs to update Bazel lockfiles.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/update-lockfiles.yaml
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.

Copy link

@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 reverts a previous commit, removing the update_lockfiles script. This is a straightforward change to reduce complexity by removing unused automation. My review includes one point of feedback to ensure a complete cleanup of related components.


set -euC

workflow=update-lockfiles.yaml

Choose a reason for hiding this comment

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

medium

With the removal of this script, the update-lockfiles.yaml GitHub workflow it triggers is likely now orphaned. To prevent dead code, please also remove the workflow file, which is probably located at .github/workflows/update-lockfiles.yaml.

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