kendo.dev

Appearance

GitHub Integration ​

kendo integrates with GitHub to connect your code with your project management workflow. Link repositories, track branches and pull requests, and automate board transitions based on GitHub events.

Connecting GitHub ​

kendo has two GitHub hookups. Most teams use both:

  • Per-user OAuth (this page) — lets each developer create branches from issues and read repos on their behalf.
  • Per-workspace GitHub App — lets kendo receive webhooks, update PR status, and auto-link branches for the whole team. Installed once by a workspace admin.

OAuth Authentication ​

Connect your GitHub account through OAuth from your profile settings. This allows kendo to access your repositories and perform actions on your behalf.

Linking Repositories ​

After connecting your account, link one or more GitHub repositories to a project. Set a primary repository for the project — this is used as the default for branch operations.

Branch Linking ​

Link Git branches to issues to track development progress:

  • Create branches directly from an issue — kendo generates a branch name based on the issue key (e.g., KD-42-fix-login-validation)
  • Link existing branches to issues for tracking
  • View branch status including open pull requests

Branch links are visible on the issue detail view, giving your team a direct connection between work items and code.

Webhooks ​

kendo receives GitHub webhooks for real-time updates:

EventWhat kendo does
Branch createdLinks the branch to the issue whose key is in its name, then runs the Branch Created lane trigger
Pull request openedSets the branch link's status to Open, runs the PR Opened lane trigger, adds a kendo check run to the PR's head commit and posts a comment on the PR with the linked issue's details
Pull request reopenedSets the status back to Open and adds a check run; it runs no lane trigger and posts no comment
New commits pushed to a pull requestAdds a check run to the new head commit
Pull request ready for reviewRuns the PR Ready for Review lane trigger
Pull request mergedSets the status to Merged and runs the PR Merged lane trigger
Pull request closed (without merging)Sets the status to Closed and runs the PR Closed lane trigger

Pull request events act only on a branch that is already linked to an issue. A lane trigger moves the issue only when one of the project's lanes holds that event; see Lane GitHub Triggers for what a move does.

Lane GitHub Triggers ​

Configure lanes to respond to GitHub events automatically. For example:

  • When a PR is opened → move the issue to "Review"
  • When a PR is merged → move the issue to "Done"

Configure triggers in the project's lane settings. Each lane can have its own trigger conditions.

To set triggers from a script, use the Lane GitHub Triggers API. It reads a project's triggers and replaces the whole set in one call.

Managing Branches via MCP ​

AI assistants can link branches through MCP tools:

"Link branch KD-42-fix-login to issue KD-42"

See the API Reference for details.

See Also ​