Probably need to think through the concrete use cases for "handle". e.g. if there are requirements related to tracking issues in some uniform way in software p

Probably need to think through the concrete use cases for "handle". e.g. if there are requirements related to tracking issues in some uniform way in software projects that have a many:many relationship with source repos, a possible solution is to use some other system for issue tracking, don't try to track issues in github. If there's a requirement to uniformly configure access controls / branch protection etc to hundreds of git repos, you could use terraform or roll your own automation using the github API combined with whatever you can enforce at the github org level.