Code tools tell the graph what shipped. Fivo reads pull requests and the conversation around them, not your source code, so a merged change can be linked to the ticket, the meeting or the incident that motivated it.
What it adds to your Brain
For each repository you choose, Fivo reads pull requests: title, description, the comments on them and the reviews. Each pull request and its thread form one episode, so a long review turns into a few facts: what changed, who reviewed, what was decided, when.
Fivo does not read commits, files or source code, and it does not write anything to GitHub.
Example question your AI can then answer: "Who asked for SSO, when was it decided, and in which pull request did it ship?"
Before you start
- A GitHub account with access to the repositories you need. Repositories from your own account, your organizations and the ones you collaborate on are all listed.
- Organization scope requires the Fivo organization owner. See Connect your tools.
- If a GitHub organization restricts third-party OAuth apps, an organization owner may need to approve Fivo there before its repositories can be read.
Step by step
- Open Integrations in app.fivo.ai and find GitHub.
- Click Connect. GitHub opens its authorization page. You approve access to your repositories, to read your organization membership, your profile and your email address. The email is used to recognise you as the person who connected.
- Back in Fivo, the connection is confirmed. In the integration's Configuration you can choose the Repositories to read; without a choice, every repository you reach is offered as a source.
- To feed your graph, go to the Brain view, connect GitHub as a source and pick the repositories to read. Archived repositories are marked as such.
What happens next
Fivo reads each repository's pull requests updated within the history window of the source, newest first, with their comments and reviews, and shows progress in the Brain view. It registers a webhook on each repository it reads, so new pull requests, comments and reviews reach your graph as they happen. Repositories are also re-read on a regular schedule.
GitHub does not tell Fivo who can read a repository. With organization scope, a repository's facts are visible to the organization owner and to the people who took part in each pull request. With personal scope only you see them. GitHub people are known by their handle and name; Fivo matches them to your colleagues by handle and name, and an owner or admin can confirm the match. See Permissions: what your Brain can see.
Disconnect
Open Integrations, select GitHub and click Disconnect. To stop reading one repository, use Remove from graph in the Brain view: its pull requests leave your graph, and you can turn it back on later.
Troubleshooting
- A repository is missing from the list. Fivo lists repositories you own, belong to through an organization, or collaborate on. If an organization restricts OAuth apps, ask its owner to approve Fivo. Fivo marks such repositories as sources it cannot access.
- Only some people are recognised. GitHub exposes handles, not emails, for other users. Confirm the match between a handle and a colleague in Fivo, or ask them to declare their handle.
- Live updates stopped. Webhooks are registered on the repositories when they are read. Re-read the source or reconnect to register them again.
Related: Connect code and project tools.
- integration
- code