Connect GitHub

Each comment becomes an issue in the repository you choose. Replies become issue comments, and the status goes both ways: closing the issue resolves the comment. The same connection lets Claude fix comments in the repository; see Fix with Claude on GitHub. Comes with every paid plan and the free trial, but not AppSumo Tier 1. On Tier 1 it shows blurred under a box saying it comes with Tier 2; see AppSumo codes.

Connect GitHub#

1. Open the menu under your name and choose Integrations.
2. On the GitHub card, press Connect GitHub and approve Drobber in GitHub.
3. Back in Drobber, choose where each project’s comments go.

To use a token instead (or where one-click isn’t offered), open Use a token instead. Create a fine-grained personal access token in GitHub with access to the repositories you want and Issues set to Read and write, and paste it into Personal access token. Only the workspace owner can connect GitHub for every project.

Choose where each project’s comments go#

Connecting GitHub doesn't send anything yet. Each project is turned on separately, and each can go to a different repository.

1. On the Integrations page, open Projects under GitHub. It shows how many projects are on, such as "0 of 4 on".
2. Next to a project, choose a repository from the list and press Turn on.

Or do it from the project: open its Settings tab, find Connected tools, press + Connect a tool, open GitHub, choose an answer to "Which repository should new comments go to?" and press Turn on. Any team member who can open the project can do this, not only the owner.

The list only offers what GitHub itself returns for the connected account, so if what you want is missing, check that account can see it. "Nothing found to send to" means GitHub returned nothing: create one there first, then reload. To move a project later, use Change on the Integrations page, or Send somewhere else in the project's Connected tools.

The list shows up to 100 repositories the account can reach, most recently updated first. Archived repositories and ones with issues turned off are left out.

What the issue contains#

The title is the comment’s number and the start of its text, and the body has the comment, who left it and where, the browser and device, links to the page and to Drobber, and developer details when Testing tools are on.

• Screenshots: GitHub can’t take uploaded files this way, so each one (up to three) is posted as a comment on the issue showing the image from Drobber.
• Replies: added as comments on the issue.
• Status: Resolved closes the issue as completed. Feedback keeps it open with a "Feedback" label. In Progress opens it and removes the label.
• Assignee: not set. GitHub issues aren’t assigned from Drobber.

Drobber comments as the GitHub account that was connected.

What comes back#

Closing an issue, for any reason, resolves the comment. An open issue with the "Feedback" label moves it to Feedback, and reopening it moves it to In Progress. Comments and assignees on GitHub don’t come back.

For instant updates, Drobber adds a webhook to the repository, which needs admin rights on it. Without them, changes come back within a few minutes instead; the project’s Connected tools says which. Fix with Claude on GitHub needs the webhook to notice Claude’s pull request.

Use a different account for one project#

In the project's Settings, under Connected tools, open GitHub and choose Use a different GitHub account for this project. Enter that account's details, press Connect GitHub, then choose where comments go and press Save. The project then shows Connected rather than On, using the workspace connection.

Turn it off or disconnect#

• One project: press Turn off next to it on the Integrations page, or in its Connected tools (Disconnect, if it uses its own connection).
• Every project: the workspace owner presses Disconnect on the GitHub card, then Disconnect GitHub. Every project using the workspace connection stops sending. Projects with their own connection carry on.

Nothing is deleted in GitHub: each issue stays where it is. Drobber does forget which issue belongs to which comment, and removes any webhook it set up there. If you turn it on again later, a new reply on an older comment starts a new issue, and status changes on older comments are not sent.