Graion Dilach

Thank you, I filed this as a PR.

Try a GUI frontend. I'll be honest, I never even bothered to learn the git CLT in these 10 years I am using it. GitExtensions on Windows and git-cola on Linux are my go-to tools and IMo are more straightforward and intuitive when it comes to interactive rebases from my experience (during some of my C&C modding projects, I've even managed to convert some teammates over to GitExt from GitHub's own GUI tool, because that confused them).

How does this work? Do you actually parse all of a GH user/organization account's repositories and then filter out them based on some internal conditions (apparently being a fork is one)? Can this be changed/expanded with the inclusion of a repository where individuals can PR their mod's metadata/requirements to be listed in the tool? This would offer the possibility for smaller individual modders to be included while it wouldn't get crowded with unnecessary buttons longterm (+ it wouldn't require 24/7 either since it would still the individual modder's responsibility to offer it's mod through the tool with filing the PR) AND it would provide better controls if the particular modder uses their GH account for other parties as well (I have my C&C history, various uni projects and noideawhatelse by now on my GH, and not all of them are forks, for example). I mean this principle works for the EET compatibility list afterall.