REPORTING_GUIDELINES

📝 Reporting Guidelines

Thank you for taking the time to report an issue or suggest a feature! If you encounter or witness any behavior that conflicts with our Code of Conduct , please follow these guidelines to report the issue. We aim to keep this project stable and user-friendly, and your feedback helps us achieve that. Please follow these steps:

❗ For Bug Reports:

• Check for Duplicates: Please search the existing issues before submitting a new one.

• Clear Description: Provide a detailed explanation of the bug. Include steps to reproduce the issue, expected behavior, and actual behavior.

• Environment Details: Mention the version of the software, operating system, and any other relevant information.

• Screenshots/Logs: Attach screenshots or log outputs if possible. Visuals help understand the problem better.

💡 For Feature Requests:

• Purpose: Describe why the feature is needed and what problem it solves.

• Proposed Solution: Explain how you think this feature should be implemented.

• Benefits: Explain how this feature will help users or improve the project.

⚠️ Note: Issues that don’t follow these guidelines might be closed without notice.

Thank you for making this project better! 🌟