MVP live
Jive is available now. Model scope hierarchies and verify integrity with criteria, claims, and evidence.
Get started
MVP live
Documentation for the live Jive MVP.
Go to app

GitHub integration

Use the GitHub App to ingest PR evidence and optionally publish a status check.

Requirements

  • GitHub organization with permission to install apps on the repositories you want to observe
  • Permission to edit branch protection rules for the target repositories

Checklist

  • [ ] Install the Jive GitHub App
  • [ ] Connect the repositories you want to observe
  • [ ] Create a scope milestone with GitHub evidence
  • [ ] Optionally require the Jive check in branch protection
  • [ ] Verify the check updates on a pull request

Install the app

  1. In Jive, go to Integrations and choose GitHub.
  2. Click Install GitHub App and select the organization.
  3. Choose the repositories you want Jive to observe.

Screenshot placeholder: Jive -> Integrations -> GitHub install flow

Observe PR evidence

After installation, return to Jive and confirm the repositories are connected. Jive starts ingesting pull request events and check data as soon as the connection is active. GitHub signals are treated as evidence by default (checks, approvals, merges).

Screenshot placeholder: Connected repositories list

Publish a status check (optional)

Jive can publish a check run that summarizes integrity and drift for a pull request. Branch protection can require this check before merges are allowed.

Require the Jive check in branch protection

  1. In GitHub, open Settings > Branch protection rules for the repository.
  2. Create or edit the rule for your default branch (for example, main).
  3. Enable Require status checks to pass before merging.
  4. Add the Jive check name to the required checks list.
  5. Save the rule.

Find the check name

Jive publishes a check name that includes your organization and scope root. Use the exact label shown in Jive or on the first PR after the check runs.

Verify integrity

  1. Create or update a pull request that matches an observed scope.
  2. Jive posts a check run with a summary of integrity and drift.
  3. When linked criteria are satisfied, the check passes and merges are allowed.

Screenshot placeholder: Jive check summary showing Drift / Unverified details

Troubleshooting

  • The Jive check does not appear: confirm the GitHub App is installed on the repo.
  • The check is not required: verify branch protection includes the Jive check.
  • The check is stuck in progress: confirm the PR maps to an observed scope.
  • Evidence is missing: ensure required checks or approvals exist in GitHub.
  • Permissions changed: reinstall the app or update repository access.