-
Notifications
You must be signed in to change notification settings - Fork 257
Add packaging.yaml for Android Studio index #143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Add packaging.yaml for Android Studio sample index
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @pedrosax, 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 introduces a new .google/packaging.yaml file, which serves as a standardized way to define metadata for samples. This file is essential for Google's internal sample packaging process, particularly for indexing and categorizing samples within Android Studio, thereby improving their discoverability and organization for developers.
Highlights
- New Packaging Metadata File: A new file,
.google/packaging.yaml, has been added to the repository. This file is crucial for defining metadata related to sample packaging for Google's internal processes. - Structured Sample Indexing: The
packaging.yamlfile provides structured information such as the sample's status, technologies used (e.g., Android, AI, Jetpack Compose), categories (e.g., Jetpack, Machine Learning), programming languages (Kotlin), target solutions (Mobile, XR, Wear), GitHub repository, difficulty level, and API references (e.g.,androidx.compose.Composable). - Android Studio Integration: This metadata is specifically intended for the Android Studio sample index, enabling better organization and discoverability of samples within the IDE.
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
-
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. ↩
There was a problem hiding this comment.
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 adds a packaging.yaml file to provide metadata for the Android Studio sample index. The metadata looks mostly correct, but I've noticed that 'XR' (Extended Reality) is listed as a technology, category, and solution. Based on the project's README.md and source code, there are no XR features implemented. I've provided suggestions to remove these references to ensure the packaging information is accurate.
| # End users may safely ignore this file. It has no relevance to other systems. | ||
| --- | ||
| status: PUBLISHED | ||
| technologies: [Android, AI, XR, JetpackCompose] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - Machine Learning | ||
| - Jetpack Compose Layouts | ||
| - Wear OS | ||
| - Android XR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| languages: [Kotlin] | ||
| solutions: | ||
| - Mobile | ||
| - XR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add packaging.yaml for Android Studio sample index