Korieo Community Docs

GitHub integration

Connect repository activity to product context while keeping engineering signals in the right perspective.

What the GitHub integration does

The GitHub integration helps connect repository activity to product context so teams can review how engineering work relates to roadmap items, documentation, and delivery signals.

Required permissions

Required permissions depend on the finalized Community integration path. Use the minimum permissions needed to read repository metadata, pull requests, commits, releases, or other supported signals.

Connecting a repository

  • Confirm GITHUB_TOKEN, GITHUB_OWNER, and GITHUB_REPO are set for the intended repository.
  • Install or authorize access for the intended repository only.
  • Verify callback URLs and environment variables.
  • Confirm connection status inside Korieo before mapping work.

Mapping engineering work to product context

Map pull requests, commits, releases, or work references back to Product Truth and roadmap items. Treat repository activity as supporting evidence, not the complete explanation of product progress.

Pull requests, commits, releases, and delivery signals

Repository signals can help explain movement from planning to execution. They should be reviewed alongside product decisions, roadmap changes, documentation, and stakeholder context.

Troubleshooting GitHub connection issues

  • Confirm GITHUB_TOKEN, GITHUB_OWNER, and GITHUB_REPO are present when GitHub integration is enabled.
  • Check that NEXT_PUBLIC_APP_URL and any configured callback or redirect origins match the URL used in the browser.
  • Verify repository permissions and installation scope.
  • Remove secrets from logs before sharing errors in an issue.