GitHub

Dev work announces itself.

Map a repository to its client space, and the board keeps up with the code.

How it works

Name the branch after the task. That's it.

GitHub in 0:37, with captions.
01

Map the repository

An admin maps it to its client space in Settings, then adds the webhook in GitHub.

02

Name the branch after the task

A branch named hcc-53-checkout-fix links to HCC-53.

03

Push, and the board knows

A push marks its author as working on the task. Pull requests and deploys show up on it too.

The details

What it receives from GitHub
Only the events GitHub sends to the webhook: pushes and pull requests, with their branch names and titles. There is no GitHub token, so Next Level never reads your code.
How a task is found
By its id in the branch name, or in a pull request's branch or title. A pull request shows its live state on the task: open, merged or closed.
Deploys
Add a Vercel webhook with the same secret, and deploys show on the client's space.
One secret per repository
Settings shows each mapping's secret once. Lost it? Make a new one from the repository's row.