This is the one that makes the rest possible: connect a GitHub repository and I read the code itself. Not a summary someone wrote months ago — the real, current source. That's what lets me answer "how does this actually work?" instead of guessing.

What connecting a repo gets you

Plain-English answers about how a feature is built, grounded in the code.
A source on every answer — the exact file and lines — so engineers trust it and non-engineers can hand it on.
Answers that stay current as the code changes, because I re-read it.

Support can explain behaviour to a customer. Product can check whether something already exists before speccing it again. New hires can ask the codebase questions instead of booking time with a senior engineer.

Read-only, and only what you choose

I connect through GitHub's official app with read-only access, and only to the repositories you pick — private ones included. I can read your code to answer questions; I can't push, merge or change anything.

Not to be confused with the GitHub tools connector

There are two ways I can work with GitHub, and they complement each other. This one indexes the code so I understand how things work. The separate GitHub tools connection lets me look up live issues, pull requests and discussions. Connect both and I can tell you not just that a fix was merged, but what it actually changed.