[GitHub Issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/quickstart) allow you to accept suggestions and track to dos for a GitHub repository. ## How to write a good GitHub Issue First and foremost, search to make sure that a similar issue doesn't already exist. Each new issue should be discrete. Use an issue template if available, otherwise **Open a blank issue**. Provide a clear and concise title that describes the issue in a way that is easy to understand and allows us to reference the issue easily. A user story is a useful format for writing issues. Provide a detailed explanation of the issue. The type of issue (bug, feature request, or other issue) will dictate the elements to include in your description (see more below). > [!tip]- Additional Resources >- [TilburgScienceHub Write GitHub Issues That Get the Job Done](https://tilburgsciencehub.com/topics/automation/version-control/start-git/write-good-issues/) >- [Dev Community: How to Write a Good Issue](https://dev.to/opensauced/how-to-write-a-good-issue-tips-for-effective-communication-in-open-source-5443) >- [NYCPlanning Tech: Writing a proper GitHub Issue](https://medium.com/nyc-planning-digital/writing-a-proper-github-issue-97427d62a20f) >