-
Notifications
You must be signed in to change notification settings - Fork 168
Add Error Reporting Documentation #468
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 Error Reporting Documentation #468
Conversation
- Create new reporting-errors.md page explaining error details workflow - Add screenshots showing error message and Error Details modal UI - Document basic vs detailed export options with decision table - Include support contact channels (email, Discord, GitHub) - Add page to sidebar after tips-and-tricks
|
Someone is attempting to deploy a commit to the Roo Code Team on Vercel. A member of the Team first needs to authorize it. |
Review complete. No issues found. The latest commit removes the "What You Can't Do" and "When to Use Each Option" sections, further streamlining the documentation. The document follows project conventions with correct HTML image tags and proper structure. Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…m reporting-errors.md
Add comprehensive error reporting documentation with step-by-step guide
Changes Made:
This documentation helps users understand how to access and share error information effectively with the support team, including when to use basic vs detailed error exports.
Important
Add
reporting-errors.mddocumentation with error reporting guide and update sidebar.reporting-errors.mdwith a step-by-step guide on error reporting.reporting-errorsto the sidebar aftertips-and-tricks.This description was created by
for 0ee7398. You can customize this summary. It will automatically update as commits are pushed.