Connect GitHub

What it does

The Fullbeam GitHub App gives Fullbeam access to the repositories you choose. Fullbeam uses it to list your merged pull requests, read their code and tests, and check out the exact commits a task needs. Without it, you can't build tasks.

Before you start

• You need the Owner role in your Fullbeam team workspace.
• You need permission to install GitHub Apps on the GitHub organization or account. If you don't have it, you can ask a GitHub owner to install it (see step 3).
• Decide which repositories to include. Start small. You can change the list later on GitHub.

Steps

1. Open your team workspace. On Overview, find Connect private engineering evidence.
2. Select Install the GitHub App. This opens the page Install Fullbeam for (your workspace).
3. If you are not an owner, you will see Ask an owner to install it instead. It opens a page where you can Copy message, Copy install link, or select Request owner approval to notify the workspace owners in Fullbeam.
4. Select Install on GitHub.
5. On GitHub, pick the organization or account, then choose the repositories. Organizations with up to 20 repositories have all of them selected by default. Larger organizations start with selected repositories only.
6. Confirm on GitHub. You are sent back to Fullbeam.

What you'll see

• After installing, Fullbeam shows Analyzing your pull requests while it prepares PR Stories for up to five open pull requests. See PR Story.
• In the background, Fullbeam imports the last 30 days of pull request history, including merged pull requests. These are the pull requests you can turn into tasks.
• If none of the selected repositories has an open pull request, you see No pull requests yet. That is fine. You can still build tasks once the merged history is imported.
• Connections in the sidebar shows GitHub, Linear and Jira cards, with connection health, scope and sync controls.

To add or remove repositories later, change the installation's repository access on GitHub.

What Fullbeam can access

The app requests these repository permissions:

• Checks: read and write
• Contents: read and write
• Issues: read
• Metadata: read
• Pull requests: read and write

It asks for no organization permissions. It receives these events: check_suite, issue_comment, issues, pull_request, pull_request_review, pull_request_review_comment and push.

Fullbeam verifies the signature of every webhook before processing it.

What Fullbeam writes to GitHub

Fullbeam writes to GitHub only in these cases:

• PR Story: a Fullbeam Review check and one Fullbeam PR summary comment that is updated in place.
• Fullbeam Qualification check: a check on the pull request's head commit. It appears only after an owner configures the GitHub qualification gate in Qualification, under Advanced release and connection controls.
• Draft review pull requests: only when you select Create draft review PR on a finished attempt. Fullbeam pushes the attempt's files to separate review branches and opens a draft pull request. It never pushes to your existing branches.

Fullbeam does not approve, request changes on, or merge pull requests. GitHub owns review and merge enforcement.

Limits

• Publishing checks and comments is built but is still being verified against production GitHub in the private preview.
• Only repositories selected in the installation are visible. Fullbeam also checks that your GitHub account can access each repository, so a copied link does not grant access.
• The Linear and Jira connections are separate. They are only needed if you want to pair a Linear or Jira issue with a merged pull request. Merged pull requests alone are enough to build tasks.

Next: Build tasks from merged pull requests.