Connect engineering outcomes
Install the GitHub App and choose which repositories can supply qualification evidence.
The GitHub App connects private work and downstream delivery outcomes to a Stack Release qualification. Fullbeam uses repository identity, commits, pull requests, checks, reviews, merge, and abandonment as evidence. It does not replace GitHub review or decide whether an individual pull request should merge.
Install the app
- Open your Fullbeam team workspace.
- Go to Settings → GitHub.
- Select Connect GitHub.
- Choose the GitHub organization or account.
- Select the repositories Fullbeam should access.
- Return to Fullbeam and confirm that the installation is connected.
Start with selected repositories. You can add or remove repositories later from the GitHub App installation settings.
Confirm the evidence connection
- Open or update a pull request in a connected repository.
- Open Connections in Fullbeam and confirm that the repository is entitled and healthy.
- Confirm that the pull request and its check outcomes appear as imported evidence.
- If PR evidence inspection is enabled, open the supporting Story from Fullbeam or the Fullbeam check on GitHub.
Fullbeam publishes the exact-commit Fullbeam Qualification check and one aggregate-only explanatory comment. New qualification states and revisions update that same comment instead of creating another. Detailed case evidence remains in the authenticated Decision Report.
What Fullbeam reads and writes
Fullbeam reads the change intent, commits, current diff, checks, review events, and lifecycle outcomes needed for release qualification and optional PR evidence inspection. It writes only its own check and summary comment. Final approvals, change requests, merges, and branch protection remain in GitHub.
Repository access is limited by both the GitHub App installation and the Fullbeam team workspace. A copied story link does not grant access.