FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

chore: add prettier to CI and project configuration by raybell-md · Pull Request #182 · gemini-cli-extensions/workspace · GitHub

chore: add prettier to CI and project configuration - #182

Merged
allenhutchison merged 9 commits into
gemini-cli-extensions:mainfrom
raybell-md:prettier-ci-clean
Jan 29, 2026
Merged

allenhutchison merged 9 commits into
gemini-cli-extensions:mainfrom
raybell-md:prettier-ci-clean

Conversation

Copy link
Copy Markdown
Contributor

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @raybell-md, 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 integrates Prettier into the project to enforce consistent code styling across the codebase. It sets up the necessary configuration files, adds Prettier as a development dependency, and provides convenient npm scripts for checking and automatically fixing formatting issues. This change aims to improve code readability and maintainability by standardizing the code style.

Highlights

  • Prettier Configuration: New .prettierignore and .prettierrc.json files are added to define formatting rules and specify paths to be ignored by Prettier.
  • Dependency Addition: Prettier is added as a development dependency in package.json and package-lock.json to enable consistent code formatting.
  • NPM Scripts: New format:check and format:fix scripts are introduced in package.json to facilitate checking and automatically fixing code formatting issues.

🧠 New Feature in Public Preview: You can now enable Memory 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/** (1)
    • .github/workflows/ci.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 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.

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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Code Review

This pull request introduces Prettier to the project for consistent code formatting, which is a great addition for maintainability. The changes include adding the necessary configuration files, package dependencies, and scripts. My review includes a minor suggestion to simplify the Prettier configuration.

Comment thread .prettierrc.json Outdated
raybell-md and others added 8 commits January 28, 2026 16:15
Force re-run of CI checks by updating tool-normalization.ts comment.
Verified local formatting passes.
- Moved lint, format, and type-check to a separate 'verify' job running once on ubuntu-latest.
- 'test' job now depends on 'verify' and only runs tests across the OS/Node matrix.
- Reduces redundant checks and speeds up the feedback loop.

allenhutchison 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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

thanks for adding the format checking. I had to run prettier to ensure that the new tests would pass, so that added a lot of changes to the PR. I also extracted the static tests from the unit test matrix so that they only run once instead of 9 times.

allenhutchison merged commit 4f12520 into gemini-cli-extensions:main Jan 29, 2026
14 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
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.

add formatting check in CI/CD

2 participants


Back | FazBrowse Home | New Git URL