GitHub logo
Engineering integrationUpdated

GitHub pull requests and Actions on an Apple TV dashboard for your office display

GitHub is where the work actually lands, but the state of it lives in a dozen tabs. Dance Party reads your repositories through GitHub's own read-only MCP server and builds an Apple TV dashboard for the engineering office display: pull requests waiting on review, whether main is green in GitHub Actions, and the release that just went out.

  • Read-only
  • OAuth connection
  • One connection per workspace
GitHub Actions on mainLive
api / CI
Passed 6 min ago
web / CI
Passed 22 min ago
api / Deploy
In progress
mobile / Build
Failed 14 min ago
web / E2E
Passed 1 hr ago
infra / Terraform plan
Passed 3 hr ago

What teams running GitHub put on the screen, and what you would ask DJ Agent to get it.

Pull requests waiting on review

For the engineering team

A review queue grows quietly, because each engineer only sees their own requests. A list of open PRs sorted oldest first, with anything past three days in red, gets reviews picked up at standup instead of at the end of the sprint.

  • Open pull requests awaiting review, oldest first
  • Age of each PR and its repository
  • Draft PRs left out, so the list is only work ready to review
  • Count of PRs open longer than three days

Ask DJ Agent“List open non-draft GitHub pull requests in our org awaiting review, oldest first, with repo and age, and mark any older than 3 days red.”

Waiting on reviewLive
Add retry to webhook worker
acme/api #1482
5d
Migrate settings page to new forms
acme/web #3310
3d
Bump Postgres driver to 3.4
acme/api #1491
2d
Offline mode for job list
acme/mobile #822
1d
Fix flaky checkout E2E test
acme/web #3318
4h

Is main green?

For engineers and whoever is running the deploy

A failed workflow on main blocks everyone who merges after it. One tile per GitHub Actions workflow, red the moment the latest run fails, turns a broken build into a two-minute fix instead of an afternoon mystery.

  • Latest GitHub Actions run on the default branch for each workflow
  • Run conclusion: success, failure, or in progress
  • How long ago each run finished

Ask DJ Agent“Show the latest GitHub Actions run on main for each workflow in acme/api, acme/web, and acme/mobile as status tiles, red when it failed.”

Workflows on mainLive
api / CI
Passed
web / CI
Passed
mobile / Build
Failed
api / Deploy
Running

Merged pull requests per day

For engineering managers and the team

Team throughput is worth watching; individual PR counts are not. Merges per day across the org show a steady week or a stuck one without ranking engineers against each other on a shared screen.

  • Pull requests merged each day over the last two weeks
  • Total merged this week
  • Merges per repository

Ask DJ Agent“Show GitHub pull requests merged per day across our org for the last 10 working days, with this week's total on top.”

PRs merged per dayLive
63this week
Mon
Tue
Wed
Thu
Fri

Latest release

For the whole company

Shipping is the thing the rest of the company rarely sees happen. The newest GitHub release, with its tag and who published it, gives sales and support a heads-up and the team a moment of credit.

  • Latest release per repository, with tag and name
  • Who published it and when
  • Releases published this month

Ask DJ Agent“Celebrate the newest GitHub release in acme/web with its tag and who published it, and count releases this month.”

Just shippedLive
NEW RELEASE
acme/web v4.12.0
Saved views and bulk export
published by Lena Fischer

What Dance Party reads from GitHub

Dance Party reads GitHub through GitHub's own remote MCP server, on its read-only endpoint, and blocks any tool that would write. It sees the repositories and organizations the connecting GitHub user can see.

Pull requests

GitHub API docs ↗
  • Open and merged PRs
    Title, number, repository, author, draft state, created and merged dates.
  • PR search
    GitHub search queries, such as review-requested or merged in the last week, across the org.

GitHub Actions

GitHub API docs ↗
  • Workflows and runs
    Each workflow's recent runs with branch, status, conclusion, and timing.

Repositories and releases

GitHub API docs ↗
  • Releases and tags
    The latest release and release by tag, with name, notes, and publisher.
  • Commits and branches
    Recent commits on a branch and the branch list.
  • Issues
    Open and closed issues with labels, assignees, and milestones, by list or search.

How to connect GitHub

Before you start

  • An owner or admin of your Dance Party workspace makes the GitHub connection.
  • A GitHub account that can see the repositories you want on screen
  • For private organization repositories, an organization owner's approval if the org restricts OAuth app access
  1. 1
    Open the Integrations page in Dance Party and scroll to GitHub.
  2. 2
    Click Connect GitHub. GitHub opens its Authorize page for Dance Party.
  3. 3
    Next to each organization you want to show, click Grant if you are an owner, or Request to ask one.
  4. 4
    Click Authorize. GitHub sends you back and the card shows Connected.
GitHub listed as Not connected on the Dance Party Integrations page, with a purple Connect GitHub button
Captured from the Dance Party app, September 30, 2026.

One GitHub connection per workspace

A workspace holds one GitHub connection, made by one GitHub user. That one sign-in covers every organization the user belongs to and has granted, so a company with several GitHub orgs usually needs only one connection.

GitHub's consent screen asks for access to private repositories (the repo scope), because GitHub's MCP server needs it to see them. Dance Party only uses the read-only MCP endpoint and blocks write tools. Revoke it any time under Settings, Applications, Authorized OAuth Apps in GitHub.

From GitHub to your office display

Once GitHub shows Connected, the rest happens in plain English. No code, no drag-and-drop.

  1. 1. Describe it. Tell DJ Agent what you want to see.

    New dashboard+ Widget
    Describe a widget in DJ Agent, or click + Widget
    DJ Agent
    DATA SOURCES
    GitHub logoGitHubConnected
    List open non-draft GitHub pull requests in our org awaiting review, oldest first, with repo and age, and mark any older than 3 days red.Send
  2. 2. It gets built. The widget lands on your board with real GitHub data.

    New dashboard+ Widget
    GitHub logoWaiting on reviewLive
    Add retry to webhook worker
    acme/api #1482
    5d
    Migrate settings page to new forms
    acme/web #3310
    3d
    Bump Postgres driver to 3.4
    acme/api #1491
    2d
    Offline mode for job list
    acme/mobile #822
    1d
    Fix flaky checkout E2E test
    acme/web #3318
    4h
    DJ Agent
    DATA SOURCES
    GitHub logoGitHubConnected
    List open non-draft GitHub pull requests in our org awaiting review, oldest first, with repo and age, and mark any older than 3 days red.Send
  3. 3. Put it on a screen. Pair an Apple TV with the six-character code it shows, then assign the dashboard.

    The Pair your Apple TV card in Dance Party, with six boxes for the code the Apple TV shows

GitHub dashboard questions

Can GitHub pull requests show on a TV in the engineering area?

Yes. Connect GitHub, ask DJ Agent for the PRs you care about, and assign the dashboard to an Apple TV running Dance Party. It refreshes on the interval you choose, as often as every 5 minutes.

Why does GitHub ask for full repo access?

GitHub's OAuth has no read-only scope for private repositories, so its MCP server needs repo. Dance Party connects to that server's read-only endpoint and refuses any tool that writes.

Can it show private repositories in our organization?

Yes, once the organization allows it. If your org restricts OAuth apps, an owner grants Dance Party on GitHub's authorize page or approves the request afterward.

Can I show GitHub Actions status for several repositories?

Yes. Name the repositories and workflows, and each one gets its own tile with its latest run on the branch you pick.

Should I put a per-engineer PR leaderboard on the wall?

Usually not. Team-level numbers, like merges per day and PRs waiting on review, read well on a shared screen, while per-person counts tend to reward the wrong things.

Can Dance Party merge, comment on, or close anything in GitHub?

No. It reads through the read-only endpoint only. It cannot merge a pull request, comment, re-run a workflow, or close an issue.

Put GitHub on every office display

Connect GitHub, describe the dashboard, and it runs on an Apple TV, refreshing on its own.

Get Started