Skip to content

Conversation

@Gorlesunilkumar
Copy link

This PR updates the Feature Request GitHub issue template to improve clarity,
structure, and overall usability for contributors and reporters.

✔ What was improved

  • Corrected YAML syntax and label formatting
  • Rewritten template text for clearer and more professional wording
  • Added detailed instructions on using GitHub issues responsibly
  • Highlighted proper support channels and security reporting procedures
  • Reduced noise by discouraging non-informative comments (+1, same here, etc.)
  • Enhanced the layout for better readability and contributor guidance

✔ Why this change is useful

A cleaner and more explicit issue template:

  • reduces duplicate feature requests,
  • guides users toward correct support channels,
  • keeps the issue tracker focused on actionable development work,
  • improves communication between maintainers and community members.

Additional Notes

This PR changes only Markdown/YAML templates and does not affect application
code or build behavior.

This update improves the Feature Request GitHub issue template to make it clearer,
more structured, and easier for contributors to follow.

Changes include:
- Fixed YAML formatting and label syntax
- Improved wording, grammar, and readability
- Added clearer instructions for users and contributors
- Updated guidance on searching existing issues
- Highlighted security reporting rules and proper support channels
- Reduced noise in notifications by discouraging unnecessary comments
- Ensured consistent section headers and formatting

This helps maintain issue quality across the repository, reduces duplicate
requests, and guides users toward the correct support paths.


Signed-off-by: Gorlesunilkumar <[email protected]>
@Gorlesunilkumar
Copy link
Author

merge it

@Gorlesunilkumar
Copy link
Author

Please merge it fast i have evaluation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants