Integrations
Connecting to GitHub
Read repositories, code, issues and pull requests. This connector cannot change anything.
Connect GitHub and Gini can read your repositories, code, issues and pull requests, and answer questions about any of them in plain English.
This connector reads. It cannot write.
Gini connects to GitHub's read-only endpoint. It cannot merge, push, comment, open a pull request, or change a setting, and that is a property of the connection rather than a preference you set. No instruction, skill or approval can widen it.
What it can do
- Browse your repositories. The authoritative list of what the connection can reach.
- Read code. Files, directories, and how a thing actually works.
- Read issues and pull requests. State, reviewers, comments, what is blocking what.
- Read commit history. What changed, when, and by whom.
How to connect
Open Integrations
app.ginicomputer.com → Integrations → GitHub.
Choose the repositories
GitHub's own authorisation screen is where you pick which repositories the connection covers. Grant what Gini needs and no more.
Come back
Gini can now answer from your code. You can widen the repository list later.
What changes anything
Nothing does. That is the whole point of this one, and it is why it is the connection to reach for when someone on your team is nervous about giving an agent access to the codebase.
| Operation | What it does | Changes anything? |
|---|---|---|
| List repositories | Inventory of what is reachable | No |
| Read files and directories | Read the code | No |
| List and read issues | Issue state and discussion | No |
| List and read pull requests | PR state, reviewers, comments | No |
| List commits | History, filtered by author or date | No |
What it's great for
- Onboarding a new engineer. "How does authentication work in this repo? Point me at the files." They will ask this in week one and would rather not ask a person for the third time.
- The update nobody wants to write. "Summarise what the platform team shipped this sprint, for the leadership post."
- Unblocking review. "Which PRs have been open more than a week, and who is each one actually waiting on?" The second half is the part a dashboard does not tell you.
- Release notes. "What changed since the last tag? Write it for the changelog."
- Answering a question about a repo nobody owns any more. Often the fastest path to an answer that would otherwise take an afternoon of archaeology.
Example routine
A Monday review-health post:
- Read open pull requests across the connected repositories.
- Flag anything open more than five days, and name who it is waiting on.
- Note anything with no reviewer assigned at all.
- Post it in the engineering channel.
Good to know
- It works within your GitHub access. A private repository you are not on stays invisible to Gini while it works for you. Two people can correctly get different answers.
- Filing goes elsewhere. Because this connection cannot write, ask Gini to file what it finds in Linear or Notion. That is usually the flow you want anyway: read where the code is, track where the team is.
- Large repositories take a moment. Reading is real work rather than a lookup, and a question spanning many repositories costs more credits than one scoped to a single repo.
- Name the repository when it matters. Gini infers from the channel otherwise, which is right more often than not, but not always.
Troubleshooting
Gini can't see a repository
Check the authorisation covers it. GitHub grants access per repository, and a repo added after you connected will not be included until you update the grant.
It asks for something it cannot do
Asking it to merge or comment will get a plain refusal, because the connection has no such tool. Nothing is broken. If you need the write action, do it yourself or route the work to a tool Gini can write to.
Answers seem out of date
Gini reads at the moment it is asked, so this is usually a branch question. Say which branch you mean.