GitHub
A studio admin installs the Kunoru GitHub App from Admin → Integrations → Install on GitHub and picks the repositories it can see.
Linking work to tasks
Section titled “Linking work to tasks”Mention a task key anywhere GitHub shows it:
- a branch name:
OBBY-12-lava-stage - a pull request title or description:
OBBY-12: lava stage - a commit message:
Fix kill bricks (OBBY-12)
The task gets a link to the pull request, branch or commit, and its activity shows when pull requests open, merge or close, and when checks pass or fail.
Moving tasks on merge
Section titled “Moving tasks on merge”In Admin → Integrations, choose a status for On merge, move tasks to (for example “Done”). When a pull request that mentions a task merges, the task moves there. Leave it on “Leave them” to move tasks yourself.
For whoever runs Kunoru
Section titled “For whoever runs Kunoru”Create one GitHub App with:
- Webhook URL
https://{your domain}/api/github/webhook, content typeapplication/json, and a webhook secret (GITHUB_WEBHOOK_SECRET). - Setup URL
https://{your domain}/api/github/installed, with “Redirect on update” on. - Read access to contents, pull requests and checks; events: Pull request, Push, Create, Check suite.
GITHUB_APP_SLUGset to the App’s URL name.