Skip to content

Conversation

@KubrickCode
Copy link
Owner

VS Code Extension used bundled Prettier while CLI used global Prettier, causing formatting differences due to version mismatch. Added local prettier as devDependency to ensure all tools use the same version (3.6.2).

@gemini-code-assist
Copy link

Summary of Changes

Hello @KubrickCode, 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 addresses a formatting inconsistency issue where the VS Code extension and CLI were using different versions of Prettier, leading to divergent code styles. The solution involves standardizing on a single, locally managed Prettier version by adding it as a devDependency and updating execution commands to use this local instance, thereby ensuring consistent code formatting across all development environments.

Highlights

  • Consistent Prettier Version: Ensured that all development tools, including the VS Code extension and CLI, use the same version of Prettier (3.6.2) to eliminate formatting inconsistencies.
  • Local Prettier Dependency: Added Prettier version 3.6.2 as a devDependency in package.json to manage it as a project-specific tool.
  • Updated Lint Commands: Modified justfile commands to use npx prettier instead of a globally installed prettier, ensuring the locally defined version is always executed.
  • Removed Global Prettier Installation: Removed the global installation of Prettier from the .devcontainer/post-create.sh script, aligning with the new local dependency approach.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/lint.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.

VS Code Extension used bundled Prettier while CLI used global Prettier, causing formatting differences due to version mismatch.
Added local prettier as devDependency to ensure all tools use the same version (3.6.2).
@KubrickCode
Copy link
Owner Author

/gemini review

Copy link

@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 effectively resolves the formatting inconsistencies by making Prettier a local development dependency, ensuring all developers and tools use the same version. The changes to remove the global installation and update the scripts to use the local version via npx are correct and well-executed. I've included a couple of suggestions to further improve code maintainability and script efficiency in justfile and .devcontainer/post-create.sh.

@KubrickCode KubrickCode merged commit 61f2646 into main Nov 14, 2025
4 checks passed
@KubrickCode KubrickCode deleted the develop/shlee/lint branch November 14, 2025 15:49
KubrickCode added a commit that referenced this pull request Nov 16, 2025
Fix formatting inconsistency between save and lint execution
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.

2 participants