Closed
Description
Code of Conduct
- I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/get-started/using-github/communicating-on-github#github-issues
What part(s) of the article would you like to see updated?
To align with our style guide, the lines in the lists under the "GitHub Issues", "Pull requests", and "GitHub Discussions" headers should:
- Have the first letter capitalized
- Have periods at the end of these lines removed, as they are not complete sentences
- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback.
- are specific to a repository, and usually have a clear owner.
- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system.
- allow you to propose specific changes.
- allow you to comment directly on proposed changes suggested by others.
- are specific to a repository.
- are like a forum, and are best used for open-form ideas and discussions where collaboration is important.
- may span many repositories.
- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base.
- often don’t have a clear owner.
- often do not result in an actionable task.
Additional information
No response