There is no need to set up a web server, or a webhook for GitHub API, or a cache / database server. You will have a fully functional GitHub bot in 10 minutes. Just fork the example, deploy your fork on work, and configure it to interact with your own GitHub repos and OpenAI keys.

The bot is a serverless function written in Rust.

In other words, this project uses GitHub Issues’ threaded messages UI as its own chat UI. You can try it by asking a question, or joining another conversation thread by leaving a comment. The bot allows GitHub users to chat with ChatGPT and each other in GitHub Issues. In this article, I will show you how to create a serverless GitHub bot. We need a simple way to connect ChatGPT API responses to an existing messaging service. In fact, the most commonly used chat UI already exists in messaging apps like Slack, Discord, and even forums (for example, GitHub Discussions). But it is difficult to create a “chat UI” in a traditional web or app framework. The “natural” UI for the ChatGPT API application is a threaded chat.There is a lot of boilerplate code unrelated to the application’s business logic. The developer also needs to manage and safeguard the API keys. The developer needs to keep track of the history and context of each conversation in a cache or database managed by the application. OpenAI provides a simple stateless API for ChatGPT.Since OpenAI released an official API for ChatGPT in March 2023, many developers and entrepreneurs are interested in integrating it into their own business operations.īut some significant barriers remain that make it difficult for them to do this:

Slack api