Conversation
This comment was marked as resolved.
This comment was marked as resolved.
Reviewer's GuideAdds standard GitHub issue templates for bug reports, feature requests, and a generic custom template to improve issue quality and structure. Flow diagram for GitHub issue template selection and submissionflowchart TD
A(User_opens_repository_issues_page) --> B(User_clicks_New_issue)
B --> C(GitHub_displays_issue_templates)
C --> D[Bug_report_template]
C --> E[Feature_request_template]
C --> F[Custom_issue_template]
D --> D1(User_fills_bug_fields_Describe_bug_To_Reproduce_Expected_behavior_Screenshots_Desktop_Smartphone_Additional_context)
E --> E1(User_fills_feature_fields_Problem_description_Solution_Alternatives_Additional_context)
F --> F1(User_fills_custom_issue_content)
D1 --> G(Submit_issue)
E1 --> G
F1 --> G
G --> H(GitHub_creates_structured_issue)
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Summary of ChangesHello @Dargon789, 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 enhances the repository's issue management by introducing standardized templates for bug reports, feature requests, and general custom issues. The goal is to improve the clarity and completeness of incoming issues, making it easier for maintainers to understand, prioritize, and address community contributions and problems. 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
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've found 3 issues, and left some high level feedback:
- The
custom.mdissue template is currently empty apart from the front matter; consider either removing it if not needed or adding guidance/questions so it serves a distinct purpose from the other templates. - All templates have
labelsandassigneesset to empty strings; if you have common triage labels or default maintainers, it may be useful to populate these to streamline issue handling.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The `custom.md` issue template is currently empty apart from the front matter; consider either removing it if not needed or adding guidance/questions so it serves a distinct purpose from the other templates.
- All templates have `labels` and `assignees` set to empty strings; if you have common triage labels or default maintainers, it may be useful to populate these to streamline issue handling.
## Individual Comments
### Comment 1
<location> `.github/ISSUE_TEMPLATE/bug_report.md:27` </location>
<code_context>
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
</code_context>
<issue_to_address>
**nitpick (typo):** Capitalize browser names in the example list (Chrome, Safari).
Since they’re proper nouns, these browser names should be capitalized to match standard product naming.
```suggestion
- OS: [e.g. iOS]
- Browser [e.g. Chrome, Safari]
```
</issue_to_address>
### Comment 2
<location> `.github/ISSUE_TEMPLATE/bug_report.md:31-33` </location>
<code_context>
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
</code_context>
<issue_to_address>
**nitpick (typo):** Capitalize Safari in the smartphone browser example.
Consider updating this to `[e.g. stock browser, Safari]` to match standard product capitalization.
```suggestion
**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, Safari]
- Version [e.g. 22]
```
</issue_to_address>
### Comment 3
<location> `.github/ISSUE_TEMPLATE/bug_report.md:32` </location>
<code_context>
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
</code_context>
<issue_to_address>
**nitpick (typo):** Consider adding a space in the device example (iPhone 6).
This will keep the example consistent with Apple’s official device naming.
```suggestion
- Device: [e.g. iPhone 6]
```
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
![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 GitHub issue templates for bug reports, feature requests, and a custom template. The bug report and feature request templates are well-structured. My feedback includes suggestions to pre-fill titles and labels to streamline issue management. The custom template appears incomplete, and I've offered a more complete version for a general-purpose issue, or it could be removed until it's fully defined.
|
@Mergifyio refresh |
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com> Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com> Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com> Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Signed-off-by: Dargon789 <64915515+Dargon789@users.noreply.github.com>
Dargon789
force-pushed
the
Dargon789-patch-1
branch
from
3e05e3f to
26943bd
Compare
|
Deployment failed with the following error: Learn More: https://vercel.com/dargon789-forge?upgradeToPro=build-rate-limit |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
✅ Pull request refreshed |
1 participant
Summary by Sourcery
Documentation: