Skip to main content

Chat with your GitHub repository

One way to ask questions about your GitHub repository is through GitHub copilot chat inside the GitHub website. Just click on the Copilot icon next to the Search field and a conversation window pops up where you can start asking questions about your repository.


Although this works quite nice, it limits you to what GitHub Copilot has to offer. The good news is that there are some tools that allow you to use your GitHub data with other LLM’s.

How does it work?

Each of these tools work in a similar way as they read through all available data(source code, documentation,  PR info,…) in your GitHub repo to build up one big context file. For example if I feed one of my repositories into Uithub, I get this file back:

This contains the full file tree, all the documentation, source code and so on…

This file can than be given to the LLM of your choice(preferably one that accepts a large token size) to ask questions about it.

Right now I’m aware of the following tools that do this:

UitHub

Available here: Easily Ask Your LLM Coding Questions

Gitingest

Available here: Gitingest

Github.gg

Available here: GitHub.gg - Repository Analysis

Any other that you now?

More information

Asking GitHub Copilot questions in GitHub - GitHub Enterprise Cloud Docs

uithub - Easily ask your LLM code questions

Gitingest

GitHub.gg - Repository Analysis

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more