Skip to content

chore: remove review-booster standing facts - #1328

Merged
exKAZUu merged 1 commit into
mainfrom
chore/remove-review-booster-facts
Sep 14, 2026
Merged

exKAZUu merged 1 commit into
mainfrom
chore/remove-review-booster-facts

Conversation

@exKAZUu

@exKAZUu exKAZUu commented Sep 14, 2026

Copy link
Copy Markdown
Member

Why

review-booster is retiring standing facts: this repository's .review-booster.jsonc holds only a facts list, whose entries are no longer maintained and will stop being read.

Requirements

  • required: remove the facts from this repository's review-booster config

Customer Summary

Reviews by review-booster no longer receive this repository's standing facts; reviewer and data-policy defaults are unchanged.

Technical Summary

The file contained no key other than facts, so it is deleted rather than left as {}; the defaults it would yield are the same.

Testing

Configuration-only change; no code reads this file outside review-booster. CI runs as usual.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 performs a cleanup of the repository configuration by removing the .review-booster.jsonc file. As the service has deprecated the use of standing facts, this file is no longer necessary, and its removal streamlines the project structure without affecting existing functionality.

Highlights

  • Configuration Cleanup: Removed the .review-booster.jsonc configuration file as the standing facts contained within are no longer maintained or required by the review-booster service.
New Features

🧠 You can now enable Memory (public preview) 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 the 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 counterproductive. 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.


The facts were old and gathered dust, / To keep them now we felt no trust. / We deleted the file with a steady hand, / To keep the repo clean and grand.

Footnotes

  1. Review the Generative AI Prohibited Use Policy, 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 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 removes a JSON file containing a testing guideline fact regarding automatic tests and runtime tools in mise.toml. There are no review comments, and I have no feedback to provide.

@exKAZUu
exKAZUu enabled auto-merge (squash) September 14, 2026 16:08
@exKAZUu
exKAZUu merged commit 1fbb6eb into main Sep 14, 2026
6 checks passed
@exKAZUu
exKAZUu deleted the chore/remove-review-booster-facts branch September 14, 2026 16:09
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