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

Add Github issue template #268

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

jschlyter
Copy link
Contributor

@jschlyter jschlyter commented Dec 12, 2024

Summary by CodeRabbit

  • New Features
    • Introduced a structured issue template for reporting Polestar API integration problems in Home Assistant.
    • The template includes sections for describing the problem, environment details, error logs, and additional information.

@jschlyter jschlyter requested a review from a team as a code owner December 12, 2024 17:08
Copy link
Contributor

coderabbitai bot commented Dec 12, 2024

Walkthrough

The changes introduce a new issue template in the GitHub repository, specifically for reporting problems related to the Polestar API integration within Home Assistant. This template includes structured sections that guide users in providing detailed information about their issues, including descriptions of the problem, environment details, error logs, and additional information. The template also emphasizes the importance of retaining all provided text to ensure effective issue resolution.

Changes

File Change Summary
.github/ISSUE_TEMPLATE.md Added a new issue template for Polestar API issues, including sections for problem description, environment details, error logs, and additional information.

Poem

In the land of code where issues arise,
A new template blooms, a welcome surprise!
With fields to fill, and logs to share,
Troubleshooting made easy, with love and care.
So hop along, dear users, don’t delay,
Report your woes, in a structured way! 🐇✨


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. (Experiment)
  • @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.

@jschlyter jschlyter merged commit f23b075 into pypolestar:main Dec 12, 2024
3 of 5 checks passed
@jschlyter jschlyter deleted the github_issue_template branch December 12, 2024 17:09
Copy link
Contributor

@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: 2

🧹 Outside diff range and nitpick comments (3)
.github/ISSUE_TEMPLATE.md (3)

1-5: Enhance the header instructions for better issue reporting

Consider adding these important points to the header:

  • Instructions to search existing issues before creating a new one
  • A link to the latest release
  • Guidelines about handling sensitive information (logs redaction)
 <!-- READ THIS FIRST:
   - Always try the latest version before reporting a bug - your issue may already have been fixed.
+  - Search existing issues to avoid duplicates: https://github.com/jschlyter/ha-polestar/issues
+  - Latest release: https://github.com/jschlyter/ha-polestar/releases/latest
   - Provide as many details as possible. Paste logs, configuration samples and code into the backticks.
+  - Remove sensitive information (tokens, passwords, IDs) from your logs and configuration
   DO NOT DELETE ANY TEXT from this template! Otherwise, your issue may be closed without comment.
 -->

13-22: Add additional environment details

Consider requesting more technical details that could be relevant for debugging.

 - Polestar API release with the issue:
 - Home Assistant Core release:
 - Operating environment (OS/Container/Supervised/Core):
+- Python version:
+- Hardware platform (if relevant):
+- Browser and version (if UI-related):

33-33: Expand the additional information section

Provide more guidance about what kind of additional information could be helpful.

 ## Additional information
+<!--
+  Please include any additional context that might be relevant:
+  - Screenshots or videos demonstrating the issue
+  - Links to related issues or discussions
+  - Information about any troubleshooting steps already attempted
+  - Whether this is a regression (worked before)
+  - Frequency of the issue (constant/intermittent)
+-->
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 34d2498 and d946d8c.

📒 Files selected for processing (1)
  • .github/ISSUE_TEMPLATE.md (1 hunks)

Comment on lines +24 to +31
## Traceback/Error logs
<!--
If you come across any trace or error logs, please provide them.
-->

```txt

```
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Enhance error logging instructions

Add more specific guidance about which logs to include and how to obtain them.

 ## Traceback/Error logs
 <!--
   If you come across any trace or error logs, please provide them.
+  Include:
+  1. Home Assistant logs (Settings -> System -> Logs)
+  2. Integration logs (enable debug logging in configuration.yaml)
+  3. Browser console logs (if UI-related)
+  
+  Use the code block below and ensure proper formatting
 -->
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## Traceback/Error logs
<!--
If you come across any trace or error logs, please provide them.
-->
```txt
```
## Traceback/Error logs
<!--
If you come across any trace or error logs, please provide them.
Include:
1. Home Assistant logs (Settings -> System -> Logs)
2. Integration logs (enable debug logging in configuration.yaml)
3. Browser console logs (if UI-related)
Use the code block below and ensure proper formatting
-->

Comment on lines +6 to +11
## The problem
<!--
Describe the issue you are experiencing here to communicate to the
maintainers. Tell us what you were trying to do and what happened.
-->

Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Structure the problem description section for better clarity

The problem description section would benefit from more specific prompts to help users provide complete information.

 ## The problem
 <!--
   Describe the issue you are experiencing here to communicate to the
   maintainers. Tell us what you were trying to do and what happened.
+  Please provide:
+  1. Expected behavior
+  2. Actual behavior
+  3. Clear steps to reproduce the issue
+  4. Any relevant configuration (remember to remove sensitive data)
 -->
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## The problem
<!--
Describe the issue you are experiencing here to communicate to the
maintainers. Tell us what you were trying to do and what happened.
-->
## The problem
<!--
Describe the issue you are experiencing here to communicate to the
maintainers. Tell us what you were trying to do and what happened.
Please provide:
1. Expected behavior
2. Actual behavior
3. Clear steps to reproduce the issue
4. Any relevant configuration (remember to remove sensitive data)
-->

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