GitHub AI agent: let a bot triage issues and pull requests

What can a bot do in GitHub?

Much of the work around code is reading and writing text: issues, reviews, release notes. A bot can take on that part, and it pairs with coding agents like Claude Code that also run in AppuBot.

• Triage issues. List new issues, group duplicates and suggest labels and owners.
• Summarise pull requests. Explain what a change does and what to look at in review.
• Draft comments. Write review comments or replies for you to approve.
• Open issues. Turn a bug report from a chat or a screenshot into a clear, reproducible issue.
• Write release notes. Gather merged pull requests since the last release into plain-language notes.
• Check status. Tell you which of your pull requests are waiting on review or failing checks.

What can you ask a bot to do in GitHub?

These are the kinds of requests that work well. Type them in the app, or send them from your phone on Telegram.

• "What pull requests are waiting for my review?"
• "Summarise PR 482 in a few lines and tell me the riskiest part."
• "Open an issue titled "Export fails on empty sheets" with the steps I just described."
• "Draft release notes from everything merged since Monday."
• "Which open issues look like duplicates of each other?"

How do you connect GitHub to AppuBot?

1. Open AppuBot on your computer.
2. Click Connect apps in the sidebar to open the Apps page.
3. Sign in once in your browser. This links AppuBot to your own account for connected apps, and you only do it the first time.
4. Find GitHub on the page and connect it. Your browser opens GitHub's own sign-in and consent screen, and you approve it there.
5. Switch GitHub on for the bots that may use it. Each bot has its own switch, so a bot you did not choose never touches it.

The same Apps page lists about 1,700 other apps. Connecting one app once makes it available to every bot you allow.

Will it ask before it changes things in GitHub?

Commenting, opening, closing, labelling or merging changes things your team sees, so on "Approve for me" the bot shows you the action and waits. Reading issues, pull requests and files goes ahead.

This follows the bot's permission choice. On "Approve for me" the bot asks before it acts in your account, and it waits as long as you take. Reads and searches go ahead without a question. On "Full access" it acts without asking, so keep that for bots you trust with the app. More in Approvals.

What should you know before relying on a bot in GitHub?

A bot works through your own GitHub account, so it can do what that account can do and nothing more. If a task fails, it tells you why in the chat instead of guessing.

Be specific about which project, folder, list or account you mean when you have several, and say once what the bot should never touch. You can save that in its memory so it applies to every chat. AppuBot is free during early access and needs no AppuBot account, and you keep using the AI plan you already have.

Which routines suit GitHub?

Repository chores repeat, which suits a routine.

• Review queue. Weekday mornings, list pull requests waiting on you.
• Stale issues. Weekly, list issues with no activity for a month.
• Friday release notes. Draft the week's notes ready for you to edit.

GitHub with computer use and Telegram

The connection reads and writes in GitHub itself. For work on code on your own computer, a bot using an agent like Codex can edit files in its folder, and computer use helps where something only exists on screen, such as a desktop app's window.

On Telegram you can ask "is the build green?" from your phone and get a short answer. A drafted review comment waits for your tap before it posts.

Is it private to use GitHub with a bot?

It uses your own GitHub account and the repositories it can reach. Code or text it reads goes to its AI provider to be answered, like using that AI yourself, so apply the same rules your team has for sharing private code with an AI.

Turn the app off for a bot at any time from its switch on the Apps page, and the bot loses access at once. You can also disconnect the app completely. See connected apps for how connections work.