Update issue templates #290
Conversation
Summary of ChangesHello @dpasiukevich, 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 standardized issue templates for bug reports and feature requests. The primary goal is to enhance the quality and consistency of submitted issues by providing clear structures and prompts for necessary information. This will help maintainers and contributors efficiently understand and address incoming reports and suggestions, ultimately streamlining the project's issue management workflow. Highlights
Using Gemini Code AssistThe 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
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 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
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces issue templates for bug reports and feature requests. The templates are well-structured and will help standardize issue submissions. I've made a couple of minor suggestions in the bug report template to fix a typo and a formatting inconsistency to improve clarity and professionalism. The feature request template looks good.
Correct formatting of model information section.
kdroste-google
left a comment
kdroste-google
left a comment
There was a problem hiding this comment.
Please consider more "structured" approach
| --- | ||
|
|
||
| ** Please make sure you read the contribution guide and file the issues in the right place. ** | ||
| [Contribution guide.](https://google.github.io/adk-docs/contributing-guide/) |
There was a problem hiding this comment.
Missing Go-specific entries in https://google.github.io/adk-docs/contributing-guide/ :
https://google.github.io/adk-docs/contributing-guide/#reporting-issues-bugs-errors
https://google.github.io/adk-docs/contributing-guide/#suggesting-enhancements
https://google.github.io/adk-docs/contributing-guide/#improving-documentation
https://google.github.io/adk-docs/contributing-guide/#writing-code
There was a problem hiding this comment.
Yes, it's a separate repo which will be handled in a separate PR.
| title: '' | ||
| labels: bug | ||
| assignees: '' | ||
|
|
There was a problem hiding this comment.
Maybe it would be better to add some structure
See
https://github.com/google/gvisor/blob/master/.github/ISSUE_TEMPLATE/bug_report.yml
There was a problem hiding this comment.
- Let's keep it in uniform with adk-python and adk-java, which this PR suggests.
- Could you clarify what you mean by structure here? The template already has the structure
There was a problem hiding this comment.
Please open https://github.com/google/gvisor/issues and create a new issue
| [Contribution guide.](https://google.github.io/adk-docs/contributing-guide/) | ||
|
|
||
| **Is your feature request related to a problem? Please describe.** | ||
| A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] |
There was a problem hiding this comment.
I always wanted to do .... instead of frustrated ? :)
| ** Please make sure you read the contribution guide and file the issues in the right place. ** | ||
| [Contribution guide.](https://google.github.io/adk-docs/contributing-guide/) | ||
|
|
||
| **Is your feature request related to a problem? Please describe.** |
There was a problem hiding this comment.
Add relations to bugs
|
|
||
| **To Reproduce** | ||
| Please share a minimal code and data to reproduce your problem. | ||
| Steps to reproduce the behavior: |
There was a problem hiding this comment.
This doesn't apply for docs issues, maybe we should have a dedicated one for that
Or we can add "other issues" for docs, questions, debt etc
There was a problem hiding this comment.
Yep, it exists by default. When issue is created you could either choose from the templates OR create a blank issue which is exactly for that.
2 participants
No description provided.