Sabaki Guide

GitHub Project Evidence Setup In Sabaki

How to connect GitHub repositories so Sabaki can preserve repository and commit evidence.

GitHub project evidence sync is the Sabaki workflow for reading permitted repositories and recent commits, then storing them as evidence items instead of KPI snapshots.

Key Takeaways

How To Sync GitHub Evidence

  1. Choose the credential typeUse a personal access token or GitHub App installation credentials with access to the relevant repositories.
  2. Connect GitHub in SabakiOpen Apps, choose GitHub, and paste the credential in the expected format.
  3. Run Sync NowSync up to the current repository and commit evidence set.
  4. Review evidenceUse Advisor or source-backed views to inspect repository and commit evidence.
  5. Rotate credentials deliberatelyReconnect GitHub if the token or GitHub App installation changes.

Quick Comparison

Synced ItemSourceWhere It Appears
Repository evidencePermitted GitHub repositoriesSource-backed project and company context
Commit evidenceRecent commits per repositorySource-backed technical progress evidence
Sync cursorRepository count and auth modeConnection sync status

Frequently Asked Questions

Does GitHub update KPIs?

No. The current GitHub connection stores evidence items rather than KPI snapshots.

How many repositories are synced?

Sabaki caps the sync to a bounded repository set and recent commits so the connection stays manageable.

Can I use a GitHub App?

Yes. The connector supports GitHub App credentials when app ID, installation ID, and private key are provided.

What should GitHub evidence be used for?

Use it to support product progress, technical readiness, and Advisor answers that need source-backed repository context.

Back to Sabaki