Skip to content

fix(wbfy): ignore local cache source checkouts - #1141

Open
exKAZUu wants to merge 1 commit into
mainfrom
fix/wbfy-ignore-cache
Open

fix(wbfy): ignore local cache source checkouts#1141
exKAZUu wants to merge 1 commit into
mainfrom
fix/wbfy-ignore-cache

Conversation

@exKAZUu

@exKAZUu exKAZUu commented Jul 29, 2026

Copy link
Copy Markdown
Member

Summary

  • ignore .cache trees during repository capability detection
  • remove stale generated Rust workflows and badges when no repository Rust code remains
  • cover the cache-detection and upgrade paths with regression tests

Verification

  • bun verify-full
  • local bun start "/Users/exkazuu/ghq/github.com/WillBooster/tokzip-corpus"

Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>
@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 improves the accuracy of repository capability detection by explicitly ignoring local cache directories. It ensures that third-party source checkouts do not trigger the generation of unnecessary Rust workflows. Additionally, it introduces cleanup mechanisms to remove stale generated workflows and README badges, ensuring the repository state remains clean when Rust code is no longer present.

Highlights

  • Cache Directory Exclusion: Updated glob patterns to ignore .cache directories, preventing third-party source checkouts from being incorrectly identified as repository Rust code.
  • Stale Workflow Cleanup: Implemented logic to automatically remove generated Rust workflows and associated README badges when no actual Rust code is detected in the repository.
  • Regression Testing: Added unit tests to verify that cached Cargo projects no longer trigger workflow generation and that stale artifacts are properly cleaned up.
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 cache was hiding code unseen, Which made the workflows turn to green. But now we prune the stale and old, And keep the repo clean and bold.

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 prevents wbfy from incorrectly detecting Rust code in local caches (such as .cache) by adding **/.cache/** to the glob ignore list. It also ensures that if a repository has no Rust code, any stale generated test-rust.yml workflow and its corresponding README badge are cleaned up. Unit tests have been added to verify these behaviors. I have no feedback to provide as there are no review comments.

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