GitHub integration is available on Pro and Scale plans where the github feature flag is enabled. It covers OAuth connection, attaching repositories to a project, and linking commits to tasks, plus GitHub-aware workflows in the product. It does not include automated pull-request review as a KaryaBoard feature. Product overview: GitHub integration.
Prerequisites
- A KaryaBoard account on Pro or Scale (or an active trial that includes GitHub).
- Permission in GitHub to authorize the OAuth connection for the repos you need.
- A KaryaBoard project that should own those repositories.
Free plans do not include GitHub. Compare limits on pricing.
Connect a project
- Sign in at https://app.karyaboard.com.
- Open the target project.
- Start the GitHub connect / OAuth flow from the project's GitHub settings.
- Approve access in GitHub when prompted.
- Select the repositories that belong to this project and save.
Agencies should map client repos to client projects to avoid cross-account commit noise. See for agencies.
Link commits to tasks
As work ships, link commits to the tasks they implement so the board shows delivery evidence beside status. Use commit linking when a task represents a concrete code change; keep design or client-approval tasks free of noisy unrelated SHAs.
KaryaBoard uses GitHub as an integration, not as your login provider. Disconnect OAuth when a repository should leave the workspace.
With Claude MCP
MCP and GitHub are complementary. Claude can create or update tasks through https://mcp.karyaboard.com/mcp while humans (or your process) link commits to those tasks. MCP setup: MCP docs.
What not to expect
Do not expect KaryaBoard to replace GitHub Actions, CODEOWNERS policy engines, or dedicated PR review bots. Those belong to GitHub and specialized tools. KaryaBoard's scope here is connect repos, link commits, and keep engineering context on the Kanban board.
Related
Getting started · MCP overview · Docs index · support@karyaboard.com