Fix checkbox syntax in PR template

[Moriyuki-S]

Summary
Fixed checkbox syntax in the pull request template to ensure checkboxes are properly rendered by GitHub.

Changes

• Updated checkbox format from - [] to - [ ] in pull_request_template.md
• Added required space between hyphen and brackets for GitHub Markdown recognition

Reference
N/A (Template fix)

Checklist

• I have read the Contribution Guidelines and used pre-commit hooks to format this commit.
• I have added all the necessary unit tests for my change. (run_model.py for model usage, test_outputs.py and/or model_validation_colab.ipynb for quality).
• (If using an LLM) I have carefully reviewed and removed all superfluous comments or unneeded, commented-out code. Only necessary and functional code remains.
• I have signed the Contributor License Agreement (CLA).

[gemini-code-assist]

Summary of Changes

Hello @Moriyuki-S, 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 addresses a minor but important formatting issue within the project's pull request template. By adjusting the markdown syntax for checkboxes, it ensures that the template's checklist items are correctly displayed and interactive on GitHub, thereby enhancing the clarity and usability of the contribution guidelines for all users.

Highlights

• Checkbox Syntax Fix: The pull request template's checkbox syntax has been corrected from - [] to - [ ] to ensure proper rendering on GitHub.
• Improved Template Readability: This change adds the necessary space between the hyphen and brackets, making the checkboxes functional and visually correct for contributors.

🧠 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 correctly addresses the issue of improperly rendered checkboxes in the pull_request_template.md file. The change from - [] to - [ ] ensures that the checkboxes are now correctly recognized and displayed by GitHub's Markdown renderer, improving the usability and clarity of the PR template. The changes are straightforward and effectively resolve the reported syntax issue.