Skip to content
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

Update issue templates #93

Merged
merged 1 commit into from
Dec 27, 2024
Merged

Update issue templates #93

merged 1 commit into from
Dec 27, 2024

Conversation

cp-pratik-k
Copy link
Collaborator

@cp-pratik-k cp-pratik-k commented Dec 27, 2024

Summary by CodeRabbit

  • New Features
    • Introduced a bug report template to streamline issue reporting.
    • Added a feature request template to standardize submissions for new features.

Copy link

coderabbitai bot commented Dec 27, 2024

Walkthrough

A new bug report and feature request template have been added to the .github/ISSUE_TEMPLATE/ directory. These templates are designed to standardize and improve the issue reporting process by providing structured guidance for users. The bug report template includes sections for issue summary, reproduction steps, environment details, and optional screenshots or logs. The feature request template helps users articulate their proposed features, problems, and potential solutions in a clear and consistent manner.

Changes

File Change Summary
.github/ISSUE_TEMPLATE/bug_report.md New bug report template with sections for issue summary, steps to reproduce, environment details, screenshots/logs, and related issues
.github/ISSUE_TEMPLATE/feature_request.md New feature request template with sections for problem description, proposed solution, alternative solutions, and additional context

Poem

🐰 Bug reports hopping in with grace,
Templates structured, leaving no trace
Of confusion or unclear design
Feature requests now perfectly align
With CodeRabbit's helpful, guiding light! 🐞✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (5)
.github/ISSUE_TEMPLATE/bug_report.md (5)

1-8: Consider adding default labels for bug reports.

Adding default labels like bug or triage would help with issue organization and workflow automation.

 name: Bug report
 about: Create a report to help us improve
 title: ''
-labels: ''
+labels: 'bug,triage'
 assignees: ''

10-13: Add character limit guidance for the summary.

Consider adding a recommended character limit to encourage concise descriptions.

 ## Summary
-Provide a concise description of the issue.  
+Provide a concise description of the issue (recommended: 200 characters or less).  
 *Example: The app crashes when uploading files to Google Drive.*

22-27: Add browser information field for web-related issues.

Since some issues might be web-related, including browser information would be helpful.

 ##  Environment Details
 - **App Version**: [e.g., 1.0.5]  
 - **Device**: [e.g., Pixel 7, iPhone 14 Pro]  
 - **OS Version**: [e.g., Android 13, iOS 17]  
 - **Network**: [e.g., Wi-Fi, Mobile Data]  
+- **Browser** (if applicable): [e.g., Chrome 119, Safari 17]
🧰 Tools
🪛 Markdownlint (0.37.0)

22-22: null
Multiple spaces after hash on atx style heading

(MD019, no-multiple-space-atx)


28-39: Fix markdown formatting issues.

The headings have extra spaces after the hash symbols, which violates markdown best practices.

-##  Screenshots or Logs (Optional)
+## Screenshots or Logs (Optional)

-##  Related Issues or Discussions
+## Related Issues or Discussions
🧰 Tools
🪛 Markdownlint (0.37.0)

28-28: null
Multiple spaces after hash on atx style heading

(MD019, no-multiple-space-atx)


32-32: null
Multiple spaces after hash on atx style heading

(MD019, no-multiple-space-atx)


40-42: Enhance the pre-submission checklist.

The checklist could be more comprehensive and should fix the markdown formatting.

-## ⚠️ Before submitting, ensure:
+## ⚠️ Before Submitting
 - [ ] The issue hasn't already been reported.
 - [ ] You're using the latest version of the app.
+- [ ] You've included all required environment details.
+- [ ] You've provided clear reproduction steps.
+- [ ] You've searched existing issues and discussions.
🧰 Tools
🪛 Markdownlint (0.37.0)

40-40: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 09761a0 and 5a870d7.

📒 Files selected for processing (2)
  • .github/ISSUE_TEMPLATE/bug_report.md (1 hunks)
  • .github/ISSUE_TEMPLATE/feature_request.md (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • .github/ISSUE_TEMPLATE/feature_request.md
🧰 Additional context used
🪛 Markdownlint (0.37.0)
.github/ISSUE_TEMPLATE/bug_report.md

22-22: null
Multiple spaces after hash on atx style heading

(MD019, no-multiple-space-atx)


28-28: null
Multiple spaces after hash on atx style heading

(MD019, no-multiple-space-atx)


32-32: null
Multiple spaces after hash on atx style heading

(MD019, no-multiple-space-atx)


40-40: Punctuation: ':'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)

.github/ISSUE_TEMPLATE/bug_report.md Show resolved Hide resolved
@cp-pratik-k cp-pratik-k merged commit e912a39 into main Dec 27, 2024
3 checks passed
@cp-pratik-k cp-pratik-k deleted the cp-pratik-k-patch-3 branch January 3, 2025 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant