[FEATURE]: Noticed we need style.yml File For Raising Enhancement related Requests

ngoworldcommunity / NGOWorld

A platform to connect and support NGOs, charities and you to build a better tomorrow.

https://ngoworld.org

MIT License

371 stars 428 forks source link

[FEATURE]: Noticed we need style.yml File For Raising Enhancement related Requests #990

Closed NarendraKoya999 closed 1 year ago

NarendraKoya999 commented 1 year ago

Description

Purpose of this Issue:

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.

Screenshots

No response

🥦 Browser

Google Chrome

Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (blank for no)
[X] I am a GSSoC23 contributor (blank for no).

github-actions[bot] commented 1 year ago

Hello @NarendraKoya999, thank you for raising the issue.

Currently, the issue is marked as https://github.com/tamalCodes/Milan/labels/%F0%9F%91%B7%F0%9F%8F%BB%E2%80%8D%E2%99%82%EF%B8%8F%20status%3A%20awaiting%20triage which means that work for this issue is on hold and we are waiting for the maintainers/owner to review it and provide you with feedback/suggestions to proceed further.

Feel free to reach out to Tamal on Twitter, or drop a mail at tamalcodes@gmail.com if you think that this issue is of critical priority.

Give us a ⭐ to show some support Happy OpenSource 🚀

NarendraKoya999 commented 1 year ago

Hi @tamalCodes . Please review on this ISSUE as soon as Possible. Thank You !

tamalCodes commented 1 year ago

@NarendraKoya999 , please learn to be paitent. The issue will be reviewed as soon my hands are free. Also go through the discussion: #995

NarendraKoya999 commented 1 year ago

@NarendraKoya999 , please learn to be paitent. The issue will be reviewed as soon my hands are free. Also go through the discussion: #995

Ok @tamalCodes 👍

tamalCodes commented 1 year ago

Hi there, though this sounds good but all the issues that we might ever have can be generalized into being either a

bug or fix
addition or feat
dx or docs

So with these generalizations at hand, it is not much needed to create more and more templates "specifically" for some particular work. It might lead to unessecary complexities for beginners and maintainers.