Guidelines for opening an issue

[ANSHIKA-26]

Discussed in #75

GitHub Guidelines for Opening an Issue

Please follow these guidelines to help maintain the quality and organization of the project. This ensures that issues are effectively tracked, addressed, and resolved.

Search for Existing Issues
if you raise an already raised issue IT WILL BE MARKED AS SPAM , and YOU WILL BE FLAGGED ! please ensure to check all issues before raising similar ones . In case you see an issue you wish to work on , you can ask to get assigned on it , in the same issue instead of raising a NEW ONE

Avoid Spamming Multiple Issues
If you have several changes related to the UI, such as footer changes, logo updates, etc., combine them under a single issue. Instead of opening separate issues for each minor adjustment, create one issue and name it appropriately, like "UI Changes". This helps keep the issue tracker clean and focused.

Do Not Ask for a Level Label
Please do not request a level label (like level1,level 2 , level 3. These labels will be assigned to you based on the issue content and review process.

example of a perfect issue -
#1374
it has all the details , no spamming , to the point changes the contributor wants to fix !