Nit issue in the .github/PULL_REQUEST_TEMPLATE.md file, link fixed

[jwren]

• Thanks for your contribution! Please replace this text with a description of what this PR is changing or adding and why, list any relevant issues, and review the contribution guidelines below.

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our [contributor guide](https://github.com/dart-lang/sdk/blob/main/CONTRIBUTING.md for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Dart contributions to our repos should follow the Dart style guide and use dart format.
• Java and Kotlin contributions should strive to follow Java and Kotlin best practices (discussion).

[gemini-code-assist]

Summary of Changes

Hello @jwren, 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 refines the .github/PULL_REQUEST_TEMPLATE.md file by addressing two minor issues. It cleans up the initial placeholder text by removing an unnecessary hyphen and, more critically, fixes a broken link to the contributor guide. These changes aim to enhance the clarity and usability of the pull request template for future contributors, ensuring they have access to correct documentation.

Highlights

• Template Formatting: Removed a superfluous leading hyphen from the initial placeholder text in the pull request template, improving its presentation.
• Broken Link Fix: Corrected a broken URL within the 'Contribution guidelines' section of the pull request template, ensuring the link to the contributor guide is now functional.

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

[jwren]

deleting this PR and re-creating, author info got merged.

[gemini-code-assist]

Code Review

This pull request addresses two minor issues in the .github/PULL_REQUEST_TEMPLATE.md file. It correctly removes a stray hyphen from an instructional line and attempts to fix a broken markdown link. While the intention to fix the link is good, the resulting markdown syntax is still invalid. I've provided a suggestion to correct the link format.

[gemini-code-assist]

Thanks for fixing the link! However, the new link syntax is also invalid because it's a nested link. To fix it, you should remove the inner link structure. I've also restored the #overview anchor from the original link, as it points to the relevant section on the page.

Suggested change

	- See our [contributor guide]([https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md](https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md) for general expectations for PRs.
	- See our [contributor guide](https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview) for general expectations for PRs.