Add 6 more official pre-commit hooks

[jbampton]

No description provided.

[cloudflare-workers-and-pages]

Deploying john-bampton with    Cloudflare Pages

Latest commit:	412b619
Status:	✅  Deploy successful!
Preview URL:	https://5f697ef5.john-bampton.pages.dev
Branch Preview URL:	https://update-pre-commit.john-bampton.pages.dev

View logs

[gemini-code-assist]

Summary of Changes

Hello @jbampton, I'm Gemini Code Assist¹! 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 significantly expands the project's pre-commit hook configuration by integrating six additional official hooks. The primary goal is to bolster code quality, enforce consistent formatting for various data files, and enhance security by automatically flagging potential issues like debug statements and exposed credentials before code is committed.

Highlights

• New Pre-Commit Hooks: Six new official pre-commit hooks have been added to the configuration to enhance code quality and security checks.
• Code Quality Checks: The added hooks include check-builtin-literals, check-json, check-toml, and check-yaml to ensure proper formatting and usage of these file types and Python literals.
• Security Enhancements: New hooks debug-statements and detect-aws-credentials (configured to allow missing credentials) are introduced to prevent accidental commits of debugging code and sensitive AWS credentials.

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

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]

Here's the code health analysis summary for commits bb7c988..412b619. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Secrets	✅ Success		View Check ↗
Python	✅ Success		View Check ↗
JavaScript	✅ Success		View Check ↗

---

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

[gemini-code-assist]

Code Review

This pull request adds several useful pre-commit hooks. However, there is a critical issue with the configuration. The revision specified for pre-commit/pre-commit-hooks is v6.0.0, which is invalid and will break the pre-commit setup. I've left a comment with details on how to fix this.