Skip to content

chore: move pull request template to correct folder#749

Merged
Its-Just-Nans merged 2 commits into
masterfrom
move-template
Mar 23, 2026
Merged

chore: move pull request template to correct folder#749
Its-Just-Nans merged 2 commits into
masterfrom
move-template

Conversation

@Its-Just-Nans

Copy link
Copy Markdown
Member

No description provided.

@Its-Just-Nans Its-Just-Nans self-assigned this Mar 22, 2026

@amazon-q-developer amazon-q-developer Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR correctly moves the pull request template to the proper location within the .github directory structure. The change restructures the PR title requirement from being a documentation item within the HTML comment to a proper checkbox template item, which follows GitHub's pull request template conventions. The implementation is correct and achieves the intended purpose stated in the PR title.


You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 focuses on improving the organization and clarity of the repository's pull request template. By moving the template to the root of the .github directory and adding a checklist item for Conventional Commits, the PR aims to streamline the contribution process and ensure consistency in pull request titles.

Highlights

  • File Relocation: The pull request moves the pull request template file from .github/PULL_REQUEST_TEMPLATE/ to .github/.
  • Template Update: The pull request updates the pull request template to include a checklist item for conforming to Conventional Commits.
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.

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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request moves the pull request template to a standard location and improves its content by making the conventional commit requirement a visible checklist item. These changes are good. However, the CONTRIBUTING.md file contains a broken link to the old template file. It would be beneficial to update this link as part of this change to avoid confusion for contributors.

@Its-Just-Nans Its-Just-Nans enabled auto-merge March 22, 2026 22:33
@Its-Just-Nans Its-Just-Nans added this pull request to the merge queue Mar 23, 2026
Merged via the queue into master with commit abc0424 Mar 23, 2026
132 checks passed
@Its-Just-Nans Its-Just-Nans deleted the move-template branch March 23, 2026 03:34
@Pr0methean Pr0methean mentioned this pull request Mar 22, 2026
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.

1 participant