Optimize formatting workflow and pre-commit hook

[GautamBytes]

This PR introduces several small improvements to the CI formatting check and the Husky pre-commit hook.

• The formatting.yml workflow is now more efficient. It uses concurrency to cancel outdated runs and paths filtering to run only when relevant files are changed.
• The Husky pre-commit hook now includes a #!/bin/sh shebang, which is a standard best practice for script portability.

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign kevin-wangzefeng
You can assign the PR to them by writing /assign @kevin-wangzefeng in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gemini-code-assist]

Summary of Changes

Hello @GautamBytes, 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 focuses on improving the efficiency and robustness of the project's development workflow. It optimizes the CI/CD pipeline for formatting checks and enhances the local pre-commit hook for better portability, aiming to streamline developer experience and reduce CI overhead.

Highlights

• CI Workflow Optimization: The formatting.yml workflow has been made more efficient by leveraging concurrency to cancel outdated runs and paths filtering to ensure it only triggers when relevant files are modified. This reduces unnecessary CI runs and speeds up feedback cycles.
• Pre-commit Hook Portability: The Husky pre-commit hook now includes a #!/bin/sh shebang. This standard best practice improves script portability and ensures consistent execution across different development environments.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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]

Code Review

This pull request improves the pre-commit hook by adding a shebang for better portability. My review focuses on making the hook more robust. I've suggested adding set -e to the pre-commit script to ensure that it correctly blocks commits when linting or formatting checks fail. This is an important change to ensure the hook functions as intended.

[GautamBytes]

/assign @Monokaix

[GautamBytes]

@Monokaix please take a look!