GitHub Integration
Kuayle connects each workspace to GitHub through an App. Repository events are matched to Kuayle issue identifiers and recorded in the issue activity feed.
Auto-linking PRs, branches, and commits
Include an identifier such as ENG-123 in a branch name, pull-request title or body, or commit message. Kuayle matches the identifier case-insensitively and records the GitHub activity on the issue.
- Works with branch names, PR titles, and commit messages
- Case-insensitive issue key matching
- Linked GitHub activity in the issue detail view
Auto-transitions
GitHub automation rules can move a matched issue when a branch is created, a pull request opens or a pull request merges. Default rules target In Progress, In Review and Done; each rule can be enabled, disabled or mapped to another status.
- Branch created → In Progress
- PR opened → In Review
- PR merged → Done
- Fully configurable transition rules
Self-configuring GitHub App
In self-hosted mode, workspace settings start GitHub’s App Manifest flow with the required permissions, callback and webhook URL. After GitHub returns the manifest code, Kuayle exchanges it for App credentials and stores them encrypted.
- Per-workspace GitHub App in self-hosted mode
- AES-256-GCM encryption for stored App credentials
- Webhook proxy or tunnel required for private networks
Webhook and WebSocket flow
Kuayle verifies GitHub webhook signatures, processes supported events and broadcasts refresh events to connected clients in the workspace. Open pages then reload the affected issue data.
- HMAC-SHA256 verification of webhook payloads
- Workspace WebSocket notification after processing
- Client refresh of affected issue data
Review Kuayle before you deploy it
Inspect the Apache 2.0 source, then follow the Docker Compose guide to run an instance on your infrastructure.