This article is a working draft; I will update it as I go. If you have yet to read the first part of this series, you can find it here. We built a tool to help us analyze GitHub issues. Below is the result in action or a page. Regarding the output: Titles are not passed through GPT, and they are raw user entries. Normalizing the title is a good next step.

TL;DR This post showcases a creative approach to analyzing issues in the Ordinal GitHub repository by leveraging the GitHub API, GPT-3.5, and GPT-4. The author demonstrates how to obtain the necessary data using the GitHub CLI, then uses GPT-4 to generate a prompt for GPT-3.5 to analyze the repository’s issues further. Some key takeaways from this analysis include the following: Automating the collection and analysis of issues and pull requests can save time and effort.