Feature: Add config.yml and styles.yml File for Raising Enhancement Requests Separately

[NarendraKoya999]

Feature description

style.yml (Custom ISSUE_TEMPLATE):

• The style.yml file, on the other hand, serves as a custom ISSUE_TEMPLATE for issues related to coding style, code formatting, and linting rules within your GitHub repository. This template helps contributors or users report code style-related concerns or seek guidance on adhering to the project's coding standards.
• The contents of style.yml might include specific questions or prompts related to coding style, requesting users to provide examples of code snippets that need formatting adjustments or explanation. Additionally, you might include instructions on how to check code against the project's style guidelines and best practices.

👀 Have you spent some time to check if this issue has been raised before?

• [X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct

[NarendraKoya999]

Hi @rohanbabbar04 . Please Review on this Issue as soon as Possible. Thank You !

[rohanbabbar04]

I did'nt understand it fully... What is the use of config.yml ? Also is the style.yml going to generate issue templates and fail if someone does'nt follow that?

[NarendraKoya999]

I did'nt understand it fully... What is the use of config.yml ? Also is the style.yml going to generate issue templates and fail if someone does'nt follow that?

See @rohanbabbar04 .For Raising Enhancement related Issues , this styles.yml Issue Template is Simple Choice.Coming to config.yml , In this file, we can write to allow Blank Issues.These two files are used in lot of Repositories in this Open source program.So, that's why I am raising this Issue.Ofcourse, as your project requirements basis on take your decision.Thank You👍

[NarendraKoya999]

Any Updates on this Issue @rohanbabbar04