-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
[Community] The Guidelines for Issues and Features #4578
Copy link
Copy link
Closed
Labels
EnglishNativeThis issue is conveyed exclusively in English.This issue is conveyed exclusively in English.
Description
Now that AI is diligently helping manage the issues, we have to set a few guidelines for everyone to uphold, so that we can avoid any unnecessary hindrances and handle issues and features with more ease.
-
Every issue must have a clear and comprehensive description for the AI to reproduce and resolve.
- It can be a bug report with detailed call stacks, a root cause analysis, a bug report with straightforward reproduction steps, or a feature request with detailed background information.
- If you have a general issue report without detailed information, you should go to Discord and discuss it with others. You should never submit an issue until you have a clear description.
- If you submit an issue with a vague description, and the AI cannot reproduce or fix it, it will be closed as "no plan" or "cannot fix."
-
Every issue will not stay open without any progress, unless it's a devoted feature.
- A clear issue will be reproduced and fixed, or closed if it cannot be fixed or there is no plan to do so.
- We won't keep an issue open and update it without any useful information, because it doesn't make sense.
- Nobody will jump into issues and try to help you with a vague issue; it just never happens.
-
The most crucial step is to reproduce a bug in a straightforward manner.
- If you cannot reproduce a bug, then it cannot be fixed by anyone.
- Consistently encountering bugs that are difficult to reproduce suggests that your architecture needs refinement.
- Look for alternative solutions if you encounter difficulties.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
EnglishNativeThis issue is conveyed exclusively in English.This issue is conveyed exclusively in English.