Skip to content

chore: add issue/pr template#24

Merged
zhaochenyang20 merged 1 commit intomainfrom
feat/issue_template
Feb 23, 2026
Merged

chore: add issue/pr template#24
zhaochenyang20 merged 1 commit intomainfrom
feat/issue_template

Conversation

@alphabetc1
Copy link
Copy Markdown
Collaborator

@alphabetc1 alphabetc1 commented Feb 23, 2026

to #22
Add issue/pr template.
It should works once this PR is merged into main.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @alphabetc1, 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 standardizes the contribution process by introducing official templates for bug reports, feature requests, and pull requests. These additions aim to streamline issue creation and PR submissions, ensuring that contributors provide all necessary information from the outset, which will improve clarity and efficiency for both contributors and maintainers.

Highlights

  • Bug Report Template: A new YAML template for bug reports has been added, including fields for description, reproduction steps, and environment details, along with a checklist for contributors.
  • Feature Request Template: A new YAML template for feature requests has been introduced, prompting for motivation and related resources, and including a checklist.
  • Pull Request Template: A new Markdown template for pull requests has been added, providing sections for motivation, modifications, accuracy tests, benchmarking, and a comprehensive checklist for contributors.
Changelog
  • .github/ISSUE_TEMPLATE/1-bug-report.yml
    • Added a new bug report template in YAML format.
  • .github/ISSUE_TEMPLATE/2-feature-request.yml
    • Added a new feature request template in YAML format.
  • .github/pull_request_template.md
    • Added a new pull request template in Markdown format.
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.

Copy link
Copy Markdown
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

The pull request introduces issue and pull request templates, which is a good practice for maintaining consistency and clarity in contributions. The templates are well-structured and cover essential information for bug reports, feature requests, and pull requests. No critical issues were found.

@zhaochenyang20 zhaochenyang20 merged commit 19ed1fb into main Feb 23, 2026
1 check passed
@alphabetc1 alphabetc1 deleted the feat/issue_template branch February 24, 2026 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants