feat(ci): add pre-commit and format code

[kevinlin09]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @kevinlin09, 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 introduces pre-commit hooks to automate code formatting and linting, ensuring code consistency and quality across the project. It integrates several popular tools such as black, flake8, pylint, eslint, stylelint, and prettier to enforce code style and catch potential issues before they are committed.

Highlights

• Pre-commit Hook Integration: Adds a .pre-commit-config.yaml file to enable pre-commit hooks for code formatting and linting.
• Code Formatting: Configures black with a line length of 79 characters for consistent code formatting.
• Code Linting: Integrates flake8 and pylint for code linting, with specific rules disabled to align with project standards.
• Code Style Enforcement: Includes eslint and stylelint for enforcing code style in JavaScript, JSX, CSS, and related files.
• Code Formatting: Integrates prettier for code formatting of Typescript and Javascript files.
• Code Formatting: Adds trailing commas to improve code readability and maintainability.

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

[gemini-code-assist]

Code Review

This pull request introduces pre-commit to enforce code style and quality, which is a great step. The formatting changes across the codebase improve consistency. However, the configurations for pylint and mypy are overly permissive, disabling many useful checks. I've left specific comments on how to improve this. I also found a few bugs that should be addressed.

[gemini-code-assist]

This line appears to have a bug. The variable max_tokens is an integer, but it's being used as a dictionary key. The intention was likely to use the string 'max_tokens' as the key. The added # type: ignore[index] suppresses a type error but doesn't fix the underlying issue.

Suggested change

	data[max_tokens] = max_tokens # type: ignore[index]
	data['max_tokens'] = max_tokens # type: ignore[index]

[gemini-code-assist]

There seems to be a bug here. super().__init__ is called with self as the first positional argument. This will cause the dictionary to be initialized with its own items, which is likely not the intended behavior. You should remove self from the call.

        super().__init__(
            task_id=task_id,
            task_status=task_status,
            results=res,
            **kwargs,
        )

[gemini-code-assist]

Similar to another comment, there seems to be a bug here. super().__init__ is called with self as the first positional argument. This will cause the dictionary to be initialized with its own items, which is likely not the intended behavior. You should remove self from the call.

        super().__init__(
            task_id=task_id,
            task_status=task_status,
            video_url=video_url,
            **kwargs,
        )

[gemini-code-assist]

Disabling docstring checks (C0114, C0115, C0116) for "quick dev" is not a good practice for a library, as it can lead to poor documentation and lower maintainability. It's better to enforce docstrings and add them where they are missing. I suggest removing these disable flags.

[gemini-code-assist]

The mypy configuration is very permissive, with many checks disabled. While this can be a starting point, it significantly reduces the benefits of static type checking. For example, --ignore-missing-imports can hide import errors. It would be beneficial to create a plan to gradually remove these disabled checks to improve the type safety and robustness of the codebase.