Skip to content

🔇 Denoiser: Add rules for Go refactoring and formatting#309

Open
lucasew wants to merge 1 commit intomasterfrom
denoiser-update-rules-1654858600233795776
Open

🔇 Denoiser: Add rules for Go refactoring and formatting#309
lucasew wants to merge 1 commit intomasterfrom
denoiser-update-rules-1654858600233795776

Conversation

@lucasew
Copy link
Owner

@lucasew lucasew commented Feb 12, 2026

This PR updates .jules/CONSISTENTLY_IGNORED.md with new rejection patterns identified from closed PRs. Specifically, it addresses repeated attempts to restructure the Go codebase structure in nix/pkgs/workspaced and the submission of PRs containing massive, unrelated formatting changes.


PR created automatically by Jules for task 1654858600233795776 started by @lucasew

Added two new rules to .jules/CONSISTENTLY_IGNORED.md based on patterns of rejected PRs:
1.  **Go Codebase Restructuring**: Documented that refactoring `nix/pkgs/workspaced` (moving packages from `drivers` or splitting `common`) is consistently rejected.
2.  **Massive Automated Formatting**: Documented that large-scale automated formatting (especially of Nix files) in unrelated PRs is rejected.

Co-authored-by: lucasew <15693688+lucasew@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @lucasew, 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 enhances the project's CONSISTENTLY_IGNORED.md documentation by formalizing two common patterns of changes that are routinely rejected during code reviews. The additions aim to streamline the review process and prevent repeated submissions of changes related to Go codebase restructuring and large-scale automated formatting, thereby improving developer efficiency and maintaining code quality standards.

Highlights

  • Go Codebase Restructuring Rule: Added a new rule to CONSISTENTLY_IGNORED.md to explicitly reject extensive structural refactoring of the Go codebase within nix/pkgs/workspaced, emphasizing the preservation of the existing drivers and common package structure.
  • Massive Automated Formatting Rule: Introduced a rule to CONSISTENTLY_IGNORED.md to reject pull requests that include large, codebase-wide automated formatting changes alongside unrelated functional changes, advocating for dedicated formatting PRs or limiting formatting to touched lines.
Changelog
  • .jules/CONSISTENTLY_IGNORED.md
    • Added a new section 'IGNORE: Go Codebase Restructuring' detailing patterns for moving or splitting Go packages in nix/pkgs/workspaced.
    • Added a new section 'IGNORE: Massive Automated Formatting' outlining patterns for submitting large, automated formatting changes across the codebase.
Activity
  • The pull request was automatically created by Jules for task 1654858600233795776, initiated by @lucasew.
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
Contributor

@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 updates .jules/CONSISTENTLY_IGNORED.md to add two new rejection patterns for Go codebase restructuring and large-scale automated formatting. The new rules are well-defined and clearly justified. I have a couple of minor suggestions to improve the formatting for better readability.

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