Connect GitHub to Bridge: issues from meetings and related PRs

What the connection adds

Where	What it does	Example
Create an issue	A quick action in the Assistant that creates a GitHub issue from the meeting	A bug described on a call becomes an issue
Find related issues & PRs	A quick action that finds issues and pull requests tied to the topics discussed	Check whether today's bug already has an issue or an open fix
Custom agents	GitHub can be selected as a tool, so an agent can create issues and pull related work when it runs	An agent you @mention after a release review lists the pull requests it touched on

Connect it

Go to Account settings and open Integrations.
Pick the Engineering category, or type GitHub into the search field.
Select GitHub and follow its connect flow.
You land back on the Integrations page, and a message confirms the connection. If GitHub returns an error, Bridge shows its message.
Create one test issue and check which repository it lands in before you rely on it.

Check first, then create

Engineering meetings often revisit known problems. Someone describes a bug that already has an issue, or a fix that is already in review.

So open the Assistant on the meeting and run Find related issues & PRs before Create an issue. If it turns up an existing issue or pull request, add to that in GitHub instead of filing a new one.

Set up GitHub so new issues land well

Issue templates. A repository can define templates and issue forms so new issues follow the same structure. Compare an issue from a meeting with your template, and fill any gaps.
Metadata. GitHub issues can carry issue types, labels and milestones. Check them on each new issue so it shows up in the right views and projects.
Linked pull requests. When a linked pull request merges into the default branch, GitHub closes the issue. Closing keywords such as "closes #10" only work when the pull request targets the default branch.

Example: a release call that finds the fix

This example is illustrative. On a release call, someone mentions that exports fail for large files, and nobody is sure whether anyone is on it.

After the call, the team runs Find related issues & PRs. It turns up the open issue and a pull request that fixes it, whose description says "closes" and the issue number. Merging it into the default branch closes the issue, and nobody files a duplicate.

Use GitHub in a custom agent

Custom agents need a paid Bridge plan. In the agent's Tools step, select GitHub from your connected tools.

Every agent responds when you @mention it in the Assistant, except external agents. That makes @mention the simplest way to test one: run it on a few meetings and check the issues it creates.

An agent with the after-every-meeting trigger runs on its own as soon as each meeting ends. If it has the GitHub tool, it can create issues then, so keep its instructions narrow, such as acting only on release reviews.

Limits and fixes

Spoken bug reports are often vague. Check the title and the steps to reproduce on any issue that came from a meeting.
Agents act whenever their triggers fire. Review an agent's instructions and triggers before you give it the GitHub tool.
No agent options: custom agents need a paid plan.
To remove the connection, select Disconnect on the GitHub card on the Integrations page.

Sources & further reading

Keep readingConnect Linear to Bridge: issues from meetings, with triage →