GitHub Issue Naming Conventions

[MFarabi619]

1. Start with a Verb: Starting the issue name with a verb can help indicate the action that needs to be taken, e.g., "Fix error on login page", "Add payment gateway integration", "Improve readability of the 'About Us' section".
2. Use Clear and Descriptive Titles: The title of an issue should succinctly describe what the issue is about. This helps others quickly understand what the issue is about without having to read the full description.
3. Keep Them Short: While it's important to be descriptive, it's also important to keep issue names reasonably short. A good rule of thumb is to keep them under 10 words.
4. Avoid Abbreviations: Unless an abbreviation is very well-known, it's better to spell out words to avoid confusion.
5. Use Labels for Additional Context: GitHub issues can be categorized with labels, adding additional context and making it easier to filter issues. For example, labels can be used to indicate priority, the type of task (bug, feature, improvement), or the area of the project it relates to.