GitHub Integration

Overview

Connect a GitHub organisation to a Kanvas AI workspace so pull requests automatically link to the tasks they implement. When a PR references a task identifier in its title or branch name, Kanvas AI surfaces the PR on the matching task card with its current status — open, draft, merged, or closed — and updates that status as the PR evolves. Merging a linked PR can also move the task to your Done column automatically.

Use it for: keeping engineering work visible on the project board without manual status updates, giving non-engineering teammates a quick read on how close a feature is to shipping, and closing the loop between code and task.

How it works

  1. A workspace owner connects a GitHub organisation from Workspace settings → GitHub integration.
  2. After approval, Kanvas AI watches the connected repositories for pull request activity.
  3. When a PR is opened, its title and branch name are scanned for any task identifier (the short identifier shown on each task card, such as the project prefix and number).
  4. Each matched task gets a PR badge — visible on the board card and in the task detail view — showing the PR’s title and status.
  5. As the PR moves through draft → open → merged, the badge updates in place. Merging a linked PR can move the task to the column that holds the Done workflow role.

Setup

  1. Open Workspace settings → GitHub integration. Only workspace owners can connect or disconnect GitHub.
  2. Click Connect GitHub, approve access to the organisation or repositories you want Kanvas AI to read, and complete the prompt.
  3. Once connected, recent PRs from the watched repositories that reference any task identifier link automatically. New PRs link as soon as they are opened.
  4. To stop the integration, click Disconnect on the same page. Past links remain on tasks but are no longer updated.

Usage

Link a PR to a task. Reference the task identifier (for example, the project prefix and number shown on the card) in your PR title or branch name. Kanvas AI does the linking — there’s no UI step.

See a PR on the board. Cards with a linked PR show a small status badge. Hover it to see the PR title; click it to open the PR on GitHub.

See all PRs for a task. Open the task detail view. A Pull requests section lists every linked PR with title, status, and a link to GitHub.

Auto-move on merge. If the project board has a column with the Done workflow role assigned (the default for new projects), merging a linked PR moves the task into that column. Adjust which column counts as Done by changing its role — see Workflow Roles.

Edge cases & limits

  • Identifier must match exactly. The PR title or branch name has to contain the task identifier as written on the card. Misspelled identifiers don’t link.
  • Multiple PRs per task. A task can have any number of linked PRs. The status badge on the card shows the most recently updated one.
  • Multiple tasks per PR. A single PR can reference multiple task identifiers. Each task gets its own badge for the same PR.
  • No code is read. The integration looks only at PR metadata (title, branch, status). It doesn’t read your code.
  • Disconnect preserves history. Disconnecting GitHub keeps past PR links visible on tasks but stops updating them.
  • AI build skills defer to the webhook. When auto-transition is enabled for a repo, the Kanvas AI build workflow (/build, /ship) detects that the webhook owns a column move (via the repo’s webhook settings) and skips its own move so the two don’t race or double-fire. If auto-transition is off, the webhook has no mapping for that event, or no repo is connected, the skill performs the move as a fallback. Either way the task lands in the right column exactly once.
  • The board moves to In Progress the moment work starts. When the build workflow picks up a task, /build pushes the task’s branch immediately — so the branch-created webhook moves the card into your In Progress column right away, rather than only when the first pull request is opened. Teammates see work begin in real time. (This needs auto-transition enabled and a branch_created column mapping; otherwise the card moves on the usual PR events.)
  • Per workspace. Each workspace connects to its own GitHub organisation. There is no cross-workspace sharing.
This site uses Just the Docs, a documentation theme for Jekyll.