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:...
While browsing through the ASP.NET Core documentation , I accidently stumbled over the IStartupFilter interface. I had no idea what it did but it triggered my interest. Let's find out together in this post what this interface does and when it can be useful. What is IStartupFilter? IStartupFilter is an interface that allows you to intercept and modify how the application's request pipeline is built. It's particularly useful when you need to: Ensure certain middleware runs before any other middleware Add middleware consistently across multiple applications Create reusable middleware configurations Modify the order of middleware registration Here's the interface definition: How IStartupFilter Works When ASP.NET Core builds the middleware pipeline, it executes all registered IStartupFilter instances in the order they were registered. Each filter can add middleware before and after calling the next delegate, creating a wrapper around the exis...