Skip to content

Conversation

@jbampton
Copy link
Member

@jbampton jbampton commented Jan 7, 2026

No description provided.

@jbampton jbampton requested a review from BaseMax as a code owner January 7, 2026 15:31
@jbampton jbampton self-assigned this Jan 7, 2026
@cloudflare-workers-and-pages
Copy link

Deploying john-bampton with  Cloudflare Pages  Cloudflare Pages

Latest commit: a00e260
Status: ✅  Deploy successful!
Preview URL: https://1dfd661a.john-bampton.pages.dev
Branch Preview URL: https://add-prettier-with-pre-commit.john-bampton.pages.dev

View logs

@jbampton jbampton added this to Turbo Jan 7, 2026
@jbampton jbampton moved this to In Progress in Turbo Jan 7, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jbampton, 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 introduces automated code formatting for YAML files by integrating Prettier into the pre-commit hook system. This change aims to enforce consistent styling for YAML configurations, improving readability and reducing stylistic debates during code reviews. Additionally, it sets up foundational pre-commit configurations for default stages and language versions, streamlining the development workflow.

Highlights

  • Prettier Integration: Prettier has been added as a pre-commit hook to automatically format YAML files, ensuring consistent styling across the repository.
  • Pre-commit Configuration: Default stages for pre-commit and pre-push have been defined, along with default language versions for Python (python3) and Node (24.12.0).
  • Configuration File Formatting: Minor formatting adjustments were applied to existing configuration files, such as .github/dependabot.yml and .github/linters/.yaml-lint.yml, to align with new formatting standards or remove unnecessary elements.

🧠 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/codeql-analysis.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.

@deepsource-io
Copy link
Contributor

deepsource-io bot commented Jan 7, 2026

Here's the code health analysis summary for commits f35619c..a00e260. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource Secrets LogoSecrets✅ SuccessView Check ↗
DeepSource Python LogoPython✅ SuccessView Check ↗
DeepSource JavaScript LogoJavaScript✅ SuccessView Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

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 introduces prettier to the pre-commit configuration to automatically format YAML files. The implementation has a couple of issues in .pre-commit-config.yaml that will prevent it from working correctly. I've provided comments with suggestions to fix an invalid Node.js version and to improve the efficiency and correctness of the prettier hook's execution. The formatting changes in other YAML files appear to be the result of this new hook.

@jbampton jbampton merged commit 43763ec into main Jan 7, 2026
22 of 38 checks passed
@jbampton jbampton deleted the add-prettier-with-pre-commit branch January 7, 2026 15:36
@github-project-automation github-project-automation bot moved this from In Progress to Done in Turbo Jan 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants