GitHub on Context Board · connects in 1 minute

GitHub Dashboard for Your Repos

Your repos' stars, open issues and today's commits, on the board you already look at.

Free for 3 days · then $6 a month · every connection included
StarsGitHub · acme/relaynow
2,41812.6%in 30 days
30 days agoToday
Open issuesGitHub · acme/api4m
14
ForksGitHub · acme/relaynow
186
3.3%vs last week
Today's commitsGit · 2 computers1m
  • Retry webhooks on 429api · main11:42
  • Stars badge reads the cached countrelay · stars-cache10:18
  • Docs for the new CLI flagsrelay · main09:31
  • Bump the SDK to 2.4.0api · main08:56
MRRStripenow
$4,212
3.8%vs last month
An example Context Board named Ship it. Every number on it is example data.
ON ONE BOARD

Connect GitHub

  1. Start your board Sign in at board.contextbolt.com with your email. Pick a template, or start from a blank canvas.
  2. Add a public repo In Connect, choose GitHub repo and type owner/name. No account, no token. The form shows the star count before you add it.
  3. Add private repos with a token On the same form, open Private? and save your own GitHub token once. The board shows open issues on any repository it can read.
  4. Link your computer for commits In Connect, open Your AI and copy the one-line command. Run it once, and the Git activity widget lists today's commits.

What to ask your agent

“Put the stars for acme/relay at the top of this board” Your agent connects the repo as a live source, not a number it looked up once, so the count keeps reading while the board is open.
“Show open issues on our private api repo” Uses the GitHub token you saved in Connect. Your agent never asks for it and never sees it.
“Arrange this board so my repo stats sit beside my MRR” Your agent lays the board out for you. Git activity, which you add from the gallery once your computer is linked, can sit in the same row.
“Build me a launch board with our stars, Show HN and a countdown” Starts from Launch week, which has the countdown, a goal, a checklist and the Show HN feed, then adds your repo's stars.

What you see from GitHub

  • See any public repo's stars, live, with no account
  • Pick forks or open issues from the same repo, one tap each
  • Count open issues on private repos with your own token
  • Watch the stars line grow with every read
  • See today's commits, your branch and what is not committed yet
  • Add commits from more than one computer, or a server
  • Keep it all next to revenue, signups and your to-dos

GitHub on Context Board: the full guide

You post the launch on Tuesday morning. By lunch the repo is open in one tab, Stripe in another and a terminal in a third, and you’re refreshing the star count like it’s a stock price.

The number matters. Having to go and look for it is the problem.

What the GitHub dashboard shows

The GitHub repo source puts a repo’s stars on the board as a number with a line under it. Type owner/name and the form shows the count before you add it. It works for any public repository, yours or anyone else’s, with no account and no token.

Want forks or open issues instead? Paste the repo’s API address, api.github.com/repos/owner/name, into Paste a link. The board offers stars, forks and open issues as one tap each.

Private repos take your own token. Save a fine-grained GitHub token once in Connect and the board shows open issues on any repository that token can read. The token is sealed on the board’s server, never shown again, and only ever sent to api.github.com.

Then there’s the work happening on your own machine. Link your computer with the one-line runner and the Git activity widget lists today’s commits, the branch you’re on and how many files have changes waiting, for the git repos in your project folders. Link a second computer, or a server, with the same line and its commits show up too.

Where the numbers come from

Stars, forks and issues come from GitHub’s public API. The board reads them on its own server while the board is open, and every read adds a point, so the line under your stars grows from the day you add the repo.

Commits come from your machine. The runner reads git in the folders you pick and sends the board the repo names, branches, change counts and today’s commit messages. Your code never leaves your computer.

If a read fails, say GitHub is having a bad hour, the widget keeps the last good number and tells you what went wrong and when. It never fills the gap with a guess.

Why put GitHub on a board

The repo is one tab of five. Revenue lives in Stripe, signups in your database, errors in Sentry. A board puts the star count beside the MRR it’s supposed to turn into, and today’s commits beside the agents writing them.

Start from the Agents template for commits and sessions, or ask your agent to add the repo to the board you already have.

Frequently asked questions

Something else on your mind? Get in touch.

Do I need a GitHub account or a token?

Not for a public repo. Stars, forks and open issues on any public repository come from GitHub's public API with no sign-in. You only save a token for private repositories.

How does the private repo part work?

Save a fine-grained GitHub token once in Connect. A token that can read the repos you pick is all it needs. The board seals it on its server, never shows it again, and only ever sends it to api.github.com. It then shows the open issues count on any repository that token can see.

Does the open issues number include pull requests?

Yes. GitHub's API counts every open pull request as an issue, so the number can run higher than the Issues tab on the repo page. When you pick it from the repo's API address, the board calls it open issues and PRs.

Where do today's commits come from?

From the runner, a small program you set up once with one line from Connect. It reads git in the project folders you choose and sends the board each repo's name, branch, how many files have changes, and today's commit messages with their times. Your code stays on your computer.

Does it change anything on GitHub?

No. The board only reads. It never opens, closes or comments on anything, and the token you give it only needs to read.

What does it cost?

Context Board is free for 3 days, then $6 a month. One plan with every connection, widget and theme. The public GitHub repo source needs no GitHub plan at all.

Your business, on one board

Free for 3 days, then $6 a month. One plan with every connection, widget and theme.

Start free trial See everything Context Board does