Skip to content

Latest commit

 

History

History
39 lines (28 loc) · 1.46 KB

File metadata and controls

39 lines (28 loc) · 1.46 KB

ISSUES

Reporting Issues

When reporting an issue, please provide the following information:

  • Description: A clear and concise description of the issue.
  • Steps to reproduce: Detailed steps to reproduce the issue.
  • Expected behavior: What you expected to happen.
  • Actual behavior: What actually happened.
  • Environment: Information about your operating system, browser, and relevant versions.
  • Code snippets: If applicable, provide code snippets that demonstrate the issue.
  • Error messages: If there are any error messages, please include them.

Issue Labels

We use labels to categorize issues. Here are some common labels:

  • bug: Indicates a confirmed bug.
  • enhancement: Indicates a feature request or enhancement.
  • documentation: Indicates an issue related to documentation.
  • question: Indicates a question about the project.
  • help wanted: Indicates an issue that is suitable for community contributions.

Contributing Fixes

If you would like to contribute a fix for an issue, please follow these steps:

  1. Fork the repository.
  2. Create a new branch for your fix (git checkout -b fix-issue-#).
  3. Make your changes and commit them (git commit -am 'Fix issue #...').
  4. Push your branch to your fork (git push origin fix-issue-#).
  5. Create a pull request.

Please ensure your pull request includes:

  • A clear description of the changes.
  • Relevant test cases, if applicable.
  • Updates to documentation, if necessary.