You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation.yml file serves as a custom ISSUE_TEMPLATE for your GitHub repository, specifically focused on documentation-related issues. When contributors or users of your project want to report documentation-related problems, improvements, or requests, they can create a new issue using this template.
The contents of documentation.yml could include prompts or guidelines to help users structure their documentation-related issue reports effectively. For example, it might ask them to provide specific details about the section/page of documentation they found confusing, suggest possible improvements, or even ask for clarifications about the issue they are experiencing.
styles.yml (Custom ISSUE_TEMPLATE):
The styles.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 styles.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.
Show us the magic with screenshots
No response
Record
I agree to follow this project's Code of Conduct
I'm a GSSoC'23 contributor
I want to work on this issue
The text was updated successfully, but these errors were encountered:
What feature?
documentation.yml (Custom ISSUE_TEMPLATE):
styles.yml (Custom ISSUE_TEMPLATE):
Show us the magic with screenshots
No response
Record
The text was updated successfully, but these errors were encountered: