Skip to content

chore: willboosterify this repo - #14

Merged
exKAZUu merged 1 commit into
mainfrom
wbfy
Aug 9, 2026
Merged

chore: willboosterify this repo#14
exKAZUu merged 1 commit into
mainfrom
wbfy

Conversation

@exKAZUu

@exKAZUu exKAZUu commented Aug 9, 2026

Copy link
Copy Markdown
Member

No description provided.

Applied @willbooster/wbfy v18.4.1.
@gemini-code-assist

Copy link
Copy Markdown

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 routine maintenance update to align the repository with the latest tooling and dependency standards. The changes focus on upgrading core build utilities, refining project configuration files, and ensuring the development environment is consistent with current project requirements.

Highlights

  • Dependency Upgrades: Updated several core dependencies, including @willbooster/wb, build-ts, and various @rolldown and @oxc-parser bindings to their latest versions.
  • Configuration Refinement: Updated bunfig.toml with a new minimum release age and a significantly expanded list of excluded packages to improve build and dependency management.
  • Environment and Tooling: Updated the local Node.js version to 24.19.0 in mise.toml and added .docker.env to the .gitignore file.
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.

Ignored Files
  • Ignored by pattern: .github/workflows/** (4)
    • .github/workflows/close-comment.yml
    • .github/workflows/release.yml
    • .github/workflows/semantic-pr.yml
    • .github/workflows/test.yml
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.


New tools take their place, Code flows smooth in quiet grace, Builds are fast and clean.

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

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 several project dependencies (including @willbooster/wb and build-ts), bumps the Node.js version in mise.toml, and refactors the bunfig.toml configuration. Additionally, the post-merge hook script is modified. Feedback on the post-merge script suggests simplifying the regular expression for matching mise configuration files to eliminate redundancy.

}

run_if_changed "(mise\.toml|\.mise\.toml|\.tool-versions|\..+-version)" "mise install"
run_if_changed "(mise\.toml|\.mise\.toml)" "mise install"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The regular expression (mise\\.toml|\\.mise\\.toml) can be simplified to \\.?mise\\.toml to eliminate redundancy and improve readability, adhering to the repository style guide.

Suggested change
run_if_changed "(mise\.toml|\.mise\.toml)" "mise install"
run_if_changed "\\.?mise\\.toml" "mise install"
References
  1. Simplify code as much as possible to eliminate redundancy. (link)

@exKAZUu
exKAZUu merged commit e310b4a into main Aug 9, 2026
6 checks passed
@exKAZUu
exKAZUu deleted the wbfy branch August 9, 2026 11:12
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