Github

Overview

Connect Groupthink to GitHub and you can turn meeting action items into real GitHub issues without leaving the app. After a meeting, Groupthink pulls out the action items. When you route one to the GitHub issue destination, Groupthink files an issue in the repository you picked, with the action item text as the title and a link back to the meeting it came from.

Connecting GitHub happens in two parts. First you add the GitHub connection from the Connections & Integrations tab and install the Groupthink GitHub App. After that, you set which repository new issues should go to.

How it works

Every action item Groupthink captures starts out unrouted. You decide where each one goes using the Route control on the action item, which you will find in a meeting recap and in your action items view. The destinations include GitHub issue, Linear, Watch, Private, and Drop.

When you choose GitHub issue, Groupthink creates an issue in your configured repository in the background. The action item then shows a link you can click to open the issue in GitHub. The same Route control sends items to Linear if you connect Linear instead.

Heads up: GitHub App installation is required

The GitHub connection uses a GitHub App, not just a personal login. To complete the connection you need to install the Groupthink GitHub App on the GitHub organization whose repositories you want to use, and grant it access to those repositories. Installing a GitHub App on an organization generally requires that you are an owner of that organization, or that an owner approves the installation.

This is not a separate paid add-on. Routing action items to GitHub is not gated behind a subscription.

Getting Started

Step 1: Connect GitHub

1. Click your profile avatar in the top right of Groupthink to open the user menu, then click User settings.
2. Open the Connections & Integrations tab.
3. In the Action item sync section, find the GitHub Issues row and click Connect.
4. On the GitHub connection screen, click Connect to GitHub. You will be redirected to GitHub.
5. Sign in to GitHub if you are not already signed in, then authorize Groupthink and install the GitHub App on the organization you want, choosing which repositories it can access.
6. After you approve, GitHub returns you to the Connections & Integrations tab, where the GitHub connection now shows as Connected.

Step 2: Choose the repository for new issues

Issues are filed in the repository you configure on the connection. Until you set one, routing an action item to GitHub will not produce an issue.

1. In User settings > Connections & Integrations, find the GitHub connection in the Action item sync section and click Manage.
2. In the Issue sync repository field, enter the repository in owner/repo form, for example acme/backend.
3. Save the connection.

Routing an action item to GitHub

1. Open a meeting recap, or open your action items view, and find the action item you want to send to GitHub.
2. Click Route on that action item.
3. Choose GitHub issue from the menu.

Groupthink creates the issue in your configured repository. Once it is created, the action item shows a launch link next to its GitHub issue label that opens the issue in GitHub. If you change your mind, you can clear the routing on the action item to send it back to needs-triage.

What the GitHub issue looks like

The issue Groupthink creates uses the action item text as its title. The body notes that it came from a Groupthink meeting and, when the information is available, includes the action item owner, surrounding context, a link back to the source meeting in Groupthink, and a due date. You can edit the issue, add assignees and labels, and work it like any other GitHub issue.

Frequently Asked Questions

Is the GitHub integration a paid feature?

No. Unlike Slack notifications, routing action items to GitHub is not behind a subscription. You do need to connect GitHub and install the Groupthink GitHub App first.

I routed an item to GitHub but no issue appeared. What should I check?

Two settings are required. First, confirm GitHub shows as Connected under User settings > Connections & Integrations. Second, click Manage on that connection and confirm the Issue sync repository field is set to a real owner/repo value that the GitHub App can access. The issue is created in the background, so it can take a moment to appear. If the connection or repository is missing, the issue is not created.

Where do I set which repository issues go to?

On the GitHub connection itself. Open User settings > Connections & Integrations, click Manage on the GitHub connection, and set the Issue sync repository field to owner/repo. This is not set per meeting; all GitHub-routed action items go to that repository.

Can I send action items to Linear instead?

Yes. The same Route control offers a Linear destination. Connect Linear from the Connections & Integrations tab the same way you connect GitHub, then configure the target Linear team on that connection.

Why does the GitHub connection ask to install an app?

Groupthink files issues through a GitHub App so it only has access to the repositories you grant. Installing the app on your GitHub organization is what gives Groupthink permission to create issues there. Installing on an organization usually requires owner permission or owner approval.

Getting Help

Questions about connecting GitHub or syncing action items to issues? Email support@groupthink.com