Product

Learn

Data sourcesApps and databases →DocsHow Orcabase works →PricingPlans and prices →
Log inGet started

GitHub + Orcabase

How fast does your code ship?

Sync GitHub through Fivetran and ask how long pull requests wait for review, how often you ship and where work gets stuck, in plain words.

Get startedHow to connect
  • Synced by Fivetran
  • Syncs every 6 hours
  • No Fivetran account needed
AgentGitHub connected

How long do pull requests wait for a first review?

Reading your GitHub data…

Pull requests waited 11 hours for a first review last week, up from 5.

  • Two people did 70% of all reviews.
  • Small pull requests got reviewed three times faster.
  • Most of the wait was overnight.

Hours to first review, by week

W1W2W3W4W511W6
How I got this· 4 steps
  1. Looked at your GitHub pull requests and reviews
  2. Measured time from opened to first review
  3. Took the median for each week
  4. Split it by reviewer and size

Example answer. Numbers are illustrative.

In plain words

How do I measure how fast my team ships on GitHub?

GitHub keeps every pull request, review and commit. Fivetran copies them into a database Orcabase hosts for you, so you can measure how long work waits for review and how often it ships.

Ask in plain words, and see shipping next to the issues and support tickets it resolves.

Ask in plain words

What you can ask about your GitHub data

The agent answers with the number, a chart and the steps it took. Keep the good answers on a dashboard.

Meet the data agent

  • How long do pull requests wait for a first review?

  • How many pull requests did we merge each week?

  • Who reviews the most, and is it balanced?

  • How long does a pull request take from opened to merged?

  • Which pull requests have been open longest?

  • How many issues were opened and closed this month?

  • Which repositories are busiest?

  • Show me merged pull requests by week and repository.

What comes in

Your GitHub data, ready to ask about.

A copy in a database Orcabase hosts for you, with its own folder for each app.

01

Pull requests

Every pull request, its status, size, author and timeline.
02

Reviews

Who reviewed what, when, and the outcome.
03

Commits

Commits, their authors and repositories.
04

Issues and labels

Issues, labels, assignees and comments.

Numbers worth defining

Define them once. Every answer agrees.

Tell Orcabase what each number means, certify it, and your dashboards, the agent and your whole team use the same one. The agent can draft these from your GitHub data.

How metrics work

  • Time to first review

    Median hours from opened to first review.

  • Time to merge

    Median hours from opened to merged.

  • Merged pull requests

    Pull requests merged each week.

  • Review load

    Reviews per person, each week.

Dashboards to start with

Your GitHub numbers at a glance.

Ask the agent to build one of these, or pin charts yourself. Share any dashboard with a link.

Shipping

4 charts
  • Merged pull requests by week
  • Time to merge
  • Time to first review
  • Open pull requests

Team

3 charts
  • Review load by person
  • Pull request size
  • Issues opened and closed

About dashboards

Better together

Ask across GitHub and the rest of your business.

The best questions need more than one app. The agent can pull from several sources for one answer.

“How long do issues wait between the last commit and done?”

GitHub + Jira

“How long does an issue wait for its pull request to merge?”

GitHub + Linear

“Did bug tickets drop after the fixes we merged?”

GitHub + Zendesk

How to connect

Connect GitHub, step by step.

  1. 1

    Find it in Sync data

    In Orcabase, go to Sync data → Add source and search for GitHub. Pick the database to sync into.

  2. 2

    Connect GitHub on Fivetran’s page

    Sign in to GitHub on Fivetran’s page and choose the repositories or organization to sync.

  3. 3

    Choose what to sync

    Back in Orcabase, tick the data you want. Only what you pick is synced, and only it counts toward your allowance.

  4. 4

    Ask away

    The first sync starts straight away. When it’s done, ask the agent about your GitHub data.

What you’ll need

  • A GitHub login with access to the repositories or organization you want.
  • The Admin role in Orcabase, and data hosting: Fivetran writes into a database Orcabase hosts for you.
At a glance
How it connects
Synced by Fivetran
How fresh
Every 6 hours, as standard.
Where your data lives
A copy in a database Orcabase hosts for you, with its own folder for each app.
Who can set it up
An admin in your organization.
Your login
You sign in on Fivetran’s own page. Orcabase never sees your password or keys.
Cost
Counts toward your monthly sync allowance: 500,000 changed rows a month, as standard.
Sync apps with FivetranStep-by-step, in the docs.

Questions

About GitHub and Orcabase

More in the docs: Sync apps with Fivetran

Does it work with private repositories?
Yes: any repository the account you sign in with can see.
Can Orcabase change anything on GitHub?
No. Orcabase only reads the synced copy.
Do I need a Fivetran account?
No. Orcabase uses its own. You sign in to GitHub on Fivetran’s page, and the data lands in a database Orcabase hosts for you, so there’s nothing else to set up or pay Fivetran for.
How fresh is my GitHub data in Orcabase?
Fivetran syncs it every 6 hours as standard, and an admin can run a sync by hand at any time. The page for each source shows when it last synced and when it syncs next.
What does syncing cost?
Counts toward your monthly sync allowance: 500,000 changed rows a month, as standard. Each distinct row that’s added or changed in a month counts once, however often it changes, and the first full copy is free. You choose which tables sync, so you only spend the allowance on what you need.

Keep exploring

More data sources

All data sources

Your GitHub data already has the answers.

Connect it, ask your first question, and pin the answers you want to see every week.

Get startedAll data sources