Connect GitHub to Unblockd.
- In GitHubA merged pull request or release names a task, like ZIP-12
- In UnblockdIt’s attached to that task as proof
- On your sponsor’s pageThe deliverable moves, with the work behind it one tap away
What it reads
Link the GitHub repositories each Unblockd project needs, then pick what to attach to a deliverable.
In GitHub
Merged PRs and releases that name a task, like ZIP-12, become its proof.
How it stays current
GitHub tells Unblockd as soon as something changes. Unblockd then reads that item again through GitHub’s API, so a change only counts once GitHub confirms it.
How you connect
An admin installs Unblockd as a GitHub App on the repositories they pick, once for the whole workspace. Unblockd keeps only the installation’s id and asks GitHub for short-lived tokens as it reads.
What your sponsor sees
Your sponsor sees the deliverable it belongs to, with the proof one tap away once that deliverable is shared with them.
How teams use it
What happens to GitHub work once it’s connected, from the first link to your sponsor’s page.
- Name the task in the pull requestPut the task’s key, like ZIP-12, in a pull request’s title, description, or branch name. When it merges, Unblockd attaches it to that task as proof.
- Releases count tooA published release that names a task is attached the same way, once per task, so the work behind a launch is one tap from its deliverable.
- Your sponsor sees the outcomeYour sponsor sees the deliverable move, with the merged work listed as its proof. They never need a GitHub account to follow progress.
See it in practice: Deliverable sign-off with proof · AI project updates through MCP
Bring your GitHub work to your sponsor.
Questions about GitHub? Write to hello@unblockd.ai.