Skip to content

Conversation

@cgwalters
Copy link

Since the repo was imported here, thanks Tulip!

Since the repo was imported here, thanks Tulip!

Signed-off-by: Colin Walters <[email protected]>
@gemini-code-assist
Copy link

Summary of Changes

Hello @cgwalters, 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 updates the README.md file to reflect the repository's recent move to a new organization. The changes ensure that all Homebrew installation instructions correctly point to the new bootc-dev organization, maintaining accurate documentation for users.

Highlights

  • README Update: The README.md file has been updated to reflect the new organization name in the Homebrew installation commands.
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

The pull request updates the Homebrew installation instructions in the README.md file to reflect the new repository location after the project's move to the bootc-dev organization. The changes involve modifying the brew install commands to use the updated repository path. No style guides were provided, so no style guide adherence was checked.

## How do I get these

```bash
brew install tulilirockz/bcvk/bcvk

Choose a reason for hiding this comment

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

high

The repository location has changed, so the install command should be updated to reflect this change. This ensures users install from the correct source.

It looks like the previous location was tulilirockz/bcvk/bcvk and it's now bootc-dev/bcvk/bcvk.

Suggested change
brew install tulilirockz/bcvk/bcvk
brew install bootc-dev/bcvk/bcvk

Copy link
Author

Choose a reason for hiding this comment

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

I read this three times and it sure looks like Gemini is just...saying I need to do what I did?

You can also download the latest dev version by running this instead:

```bash
brew install --head tulilirockz/bcvk/bcvk

Choose a reason for hiding this comment

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

high

Similar to the previous change, the --head install command should also be updated to reflect the new repository location. This ensures users installing the development version use the correct source.

It looks like the previous location was tulilirockz/bcvk/bcvk and it's now bootc-dev/bcvk/bcvk.

Suggested change
brew install --head tulilirockz/bcvk/bcvk
brew install --head bootc-dev/bcvk/bcvk

Copy link

@tulilirockz tulilirockz left a comment

Choose a reason for hiding this comment

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

Looks great!

@cgwalters
Copy link
Author

Do you want to continue to be a maintainer/reviewer here?

@tulilirockz
Copy link

I'd be fine with it, I'm not 1000% familiar with homebrew but this is meant to be highly automated anyways

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