I would love it if there were a massive, correctly-tagged list of starter templates for all kinds of combinations of frameworks/libraries. The question is, how

I would love it if there were a massive, correctly-tagged list of starter templates for all kinds of combinations of frameworks/libraries. The question is, how should you manage that list? One idea I've been implementing for fun lately is a git repository where each branch represents a combination of optional features that can be generated. E.g., the branch `aad/aspnetcore/hotchocolate` is the starter code for an ASP.NET Core GraphQL server that uses Azure Active Directory for authentication. Whenever I make a change in the aad/develop branch, it automatically merges to aad/aspnetcore, aad/aspnetcore/hotchocolate, aad/aspnetcore/rest, etc. The problem is there are a lot of merge conflicts as you can imagine.