GitHub
Your GitHub issues, in one queue.
Open issues from the repositories you choose arrive as Inbox suggestions beside your email and Slack. Accept one and the task shows its issue and linked pull requests, while Kernel never writes to GitHub.
Highlights
Read-only on GitHub
The GitHub App asks only for read access to metadata, issues, and pull requests. Kernel never comments on, closes, or changes anything on GitHub.
Issues stay current
Edits, labels, and assignees update a waiting suggestion, keeping the fields you changed. Closing an issue withdraws it, and reopening brings it back.
Pull requests find their task
Task keys in a pull request's title, body, or branch link it to the task. So does closing a linked issue, like “Fixes #214”.
Choose what counts
Pick the repositories and whose issues.
Choose repositories on GitHub's install page, then narrow intake in Kernel: all readable repositories or selected ones, and issues assigned to Me, Unassigned, Me or unassigned, or Anyone.
- Preview the matching open issues before the first import
- Archived repositories never produce suggestions
- Pull requests are never suggested, only linked
Routing
Each repository goes to the right client.
Exclusions run first, then destination rules in order, matching on repository, label, author, or assignee. Anything left goes to the connection's default destination.
- Exclusions always win, and the top destination rule wins
- Add an AI condition in plain words when a field isn't enough
- AI never judges whether an issue is important
Good to know
- Each GitHub account or organization you install the App on is its own connection.
- Kernel keeps no GitHub sign-in token after you connect.
- Closing a linked GitHub issue offers a Kernel completion suggestion for your review.
- Webhooks deliver changes as they happen, and a sweep every 10 minutes catches anything missed.
- Kernel stores an issue's title, body, labels, assignees, and latest 10 comments, encrypted.
- Pull request bodies are scanned for task keys in memory and never stored.
- Closing an issue or merging a pull request never changes a task's status.