docs: clarify relationship between this repo and the Seed Project

[sambilbow]

Hey! I struggled somewhat with the lack of documentation around what is referred to once in the README as a Seed Project.

It is not elaborated on in the README whether or not creating the Seed Project is part of this repo's scope (though to someone with an understanding / experience of bootstrapping I'm sure this is obvious).

I think the documentation would be clearer if it:

• provided a minimal working example of a Seed Project in the GLOSSARY
• referred to the Seed Project as the users' rather than 'the Seed Project'.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Summary of Changes

Hello @sambilbow, 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 enhances the documentation by providing clearer guidance on the "Seed Project" concept. It addresses previous ambiguities by adding a practical gcloud command example for creating a Seed Project and refining the language in the README to emphasize the user's ownership of this project, ultimately making the setup process more straightforward for new users.

Highlights

• Documentation Clarity: Clarified the relationship between this repository and the concept of a "Seed Project" to improve user understanding.
• Seed Project Example: Added a minimal working example in the GLOSSARY for how to create a Seed Project using gcloud CLI commands.
• Terminology Refinement: Updated the README to refer to "your existing Seed Project" for better user-centric language.

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 aims to clarify the concept of a 'Seed Project' by updating the documentation. The changes in README.md make it clearer that the seed project must already exist. The addition of a minimal working example in docs/GLOSSARY.md is a great idea. I've provided a couple of suggestions to improve the clarity and correctness of the documentation changes. Specifically, I've pointed out a grammatical error and a non-functional code example that should be corrected to avoid confusion for users.