Create the Search Issues Route

Before implementing our API to search GitHub issues, it’s good to understand what the issues actually are. On GitHub, issues are a fundamental part of project management and collaboration. They’re used to track and discuss problems, tasks, feature requests, or general topics related to a repository. Some common types of issues we might find on GitHub are listed below:

• Bug report: Users report issues they encounter while using the software, highlighting unexpected behavior, errors, or crashes.

• Feature request: Users suggest new features or improvements they would like to see implemented in the project.

• Enhancement: These are issues discussing enhancements to existing features, such as performance improvements, usability enhancements, or design changes.

• Documentation: These are issues related to missing, unclear, or outdated documentation that need to be addressed.

• Discussion: These are issues created to facilitate discussions around a particular topic, such as architecture decisions, project direction, or community feedback.

These are just a few examples, and the specific types of issues can vary depending on the project and its guidelines. Issues serve as a central place for communication and collaboration among project contributors and the community.

Explore the GitHub search issues API

Let’s first do some exploration of the GitHub search issues API using the axios module. We’ll search the issues that consist of the keyword redis. This helps us find issues based on our skill set and make open-source contributions.