GitHub
Connect GitHub once and Naumu keeps your memory up to date from pull requests, commits, issues, reviews, releases and deploys - without reading your code.
Most of what your team ships happens in GitHub, and until now Naumu only knew about it when someone logged it. Connect GitHub to a Naumu space and your memory keeps up on its own: a pull request that merges moves its task to done, a failed deploy is recorded, and a new issue becomes a task.
Connect GitHub
- Open the space you want GitHub to feed.
- Go to Settings → Integrations and select Connect GitHub on the GitHub card.
- On GitHub, install the Naumu AI app: pick the organization or account, then All repositories or the ones you choose, and select Install.
- You're back in Naumu, connected.
A few things to know:
- You must be an owner or admin of the space.
- Installing needs a GitHub organization owner. If you aren't one, GitHub sends your owner an install request. Once they approve it, select Connect GitHub again to finish.
- One GitHub account feeds one space. A space can take several (for example your organization and a personal account). Use Add another GitHub account.
- Only new activity comes in. Naumu starts from the moment you connect. To bring in history, ask your coding agent.
What Naumu does with GitHub activity
Each piece of work gets its own thread in the #github topic: one per pull request, issue and discussion, one per branch that has no pull request yet, and one per repository per day for pushes to the main branch, tags, releases, deploys and CI.
When the activity on a thread goes quiet (about ten minutes, or a minute for a merge, a close or a failure), Naumu reads the new events and updates the space. It finds the task, feature or decision the work belongs to (including work your coding agents logged), moves statuses, records merges, releases and incidents, and creates a task only when the work is new and not a routine chore. It then replies in the thread with a line naming what it changed.
| Event | What Naumu does |
|---|---|
| Branch created, pull request opened | Moves the matching item to in progress |
| Changes requested, approved | Notes the review |
| Merged | Marks the item done, deploy not yet confirmed |
| Closed without merging | Leaves the status and asks the owner |
| Issue opened | Creates a task or bug if nothing covers it |
| Release published, deploy succeeded | Records the version as shipped |
| Deploy or CI failed on the main branch | Records an incident |
Routine noise (passing CI runs, label changes, bot pull requests like Dependabot) never reaches a thread.
Quiet by design
The #github topic is set to notify on people only. Its threads never ping anyone or show up in Focus until a person replies in one or someone is tagged. When Naumu needs an answer (for example, a pull request closed without merging), it tags the owner.
Every morning Naumu writes a GitHub digest thread: what shipped, what's in review, what's stuck and any incidents, and it fixes statuses the per-thread updates missed. Turn it off per account with the Daily digest switch.
Your code stays yours
The Naumu AI GitHub app asks for read access, including repository contents, because GitHub only sends push, tag and release events to apps that have it. Naumu only listens to events and never calls GitHub to read files. What arrives is titles, descriptions, comments, commit messages, author names, file names and change counts. Code shown next to review comments is dropped before anything is saved.
Text from people outside your organization (on public repositories) is marked, and Naumu treats it as information, never as instructions.
Disconnect
On the GitHub card, select Disconnect next to the account. Threads already in #github stay. To remove the app from GitHub as well, use Manage on GitHub.