GitHub + clariBI
Connect GitHub with no API key, choose the repositories to track, and get weekly commit activity sitting next to the delivery and outcomes it moves with.
Native GitHub data-source connector, no key needed.
Pick the repositories to track, and clariBI syncs their weekly commit activity into preprocessed datasets and auto-generated dashboards, right next to your other tools. Public repository stats read with no API key.
What is GitHub?
GitHub hosts the code repositories most software teams build in, and its REST API publishes per-repository statistics including the weekly commit activity for the last year.
clariBI reads the GitHub repository statistics API: the weekly commit count for the repositories you choose, over the last 52 weeks. You type the "owner/repo" names, and the connector reads the stats read-only. No API key is required for public repositories.
Learn more at github.com
Connect GitHub in three steps
Open Data Sources in clariBI
In clariBI, go to Data Sources → Add Data Source and find GitHub. There is no API key to paste for public repositories, so you go straight to choosing repositories.
Choose repositories
Type the repositories to track in "owner/repo" form (for example vuejs/core). clariBI reads the weekly commit activity read-only.
Sync, then get dashboards
clariBI syncs the weekly commit counts, preprocesses them, and builds an insights dashboard. Ask "How did commit activity track our release cadence?" and the AI engine queries the synced stats alongside your business data.
What you can analyze
Out of the box with the GitHub connector:
- Weekly commit count per repository over the last year
- Commit trend and week-over-week change
- Relative activity across the repositories you track
- Activity dips and spikes lined up with milestones
- Engineering cadence next to your release or revenue dates
- Cross-source: commit activity → release timing → revenue
GitHub is one of many data sources you can connect to clariBI. See the full list →
What gets synced
clariBI pulls the last 52 weeks of commit activity for the repositories you select through the GitHub REST API, lands it as a preprocessed dataset, and refreshes it on your schedule. Access is read-only.
For each selected repository, clariBI syncs the weekly commit count, then builds an insights dashboard you can query, extend, or pull into reports.
clariBI only ever reads. It never pushes, opens issues, or changes anything in the repository.
Cross-source questions GitHub makes possible
GitHub data is most useful next to your other tools. clariBI's planner composes it with your CRM, billing, and product data through the same entity-join primitives that back every cross-source analysis.
GitHub × Releases
"Did commit activity ramp before each major release?"
Planner: read weekly commits from GitHub, mark your release dates, and report the activity ramp in the weeks before each release.
GitHub × Revenue
"Did engineering velocity track our feature-driven revenue?"
Planner: read weekly commit activity from GitHub, align to revenue by week, and report where delivery and outcomes moved together.
GitHub connector FAQ
Do I need an API key for GitHub?
No, not for public repositories. clariBI reads the public commit-activity stats with no token. The connector reads read-only and never changes anything.
Why did my first sync show no data for a repository?
GitHub computes repository statistics on demand. The first request for a repository can return an empty result while GitHub builds the stats; the next sync returns the full 52-week series. A re-sync resolves it.
Which clariBI plan includes the GitHub connector?
Data-source connectors are available on the Trial, Starter, Professional, and Enterprise plans. You can connect GitHub during the free 14-day trial.
Start your free trial and connect GitHub in a minute
No key needed, read-only, synced dashboards in seconds.
Start free trial