Update report-bug.md to match v1.6.0

[tredondo]

I'm surprised that nobody cared to update this, despite all the bugs filed since the location of "Copy Debug Information" has changed.

Summary by CodeRabbit

• Documentation
  • Updated bug report instructions to simplify copying debug information.
  • For general issues, users now click the 🛠️ icon in the bottom left followed by "Copy Debug Info."
  • For app-related issues, users are guided to navigate via the app’s "Details" tab to locate the "Debugging" section and then select "Copy Debug Information."

[CLAassistant]

All committers have signed the CLA.

[coderabbitai[bot]]

📝 Walkthrough

Walkthrough

The pull request updates the bug report template by modifying the instructions provided to users on how to obtain debug information when reporting issues. For general issues, it now directs users to click the 🛠️ icon in the bottom left and then select "Copy Debug Info" instead of using the previous settings page option. For app-related issues, the steps have been revised to navigate through the app’s Details tab to the Debugging section before copying the debug information. There are no changes to exported or public entities.

Changes

File	Change Summary
.github/ISSUE_TEMPLATE/report-bug.md	Updated instructions for copying debug information: - General issues: Replaced “Click on 'Copy Debug Information' on the Settings page” with “Click on the 🛠️ icon in the bottom left, then 'Copy Debug Info'.” - App-related issues: Revised navigation steps to reach and copy debug info.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 98137ca4b61ed8ba9457dc7c1b0ad4ac8099b11f and 4ae9d989296ffe49105f89e780f47de6729cd3a0.

📒 Files selected for processing (1)

• .github/ISSUE_TEMPLATE/report-bug.md (1 hunks)

🔇 Additional comments (1)

.github/ISSUE_TEMPLATE/report-bug.md (1)

34-35: Clear and Updated Debug Instructions.
The updated instructions for both general and app-related issues now clearly reflect the new UI flow introduced in v1.6.0. Ensuring users are directed to click the 🛠️ icon in the bottom left for general issues and to navigate via the app's "Details" tab for app-related issues greatly improves clarity. Please verify that these instructions match the actual in-app behavior.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.