The worktrees in this case are git branches, though. While this is convenient in some cases, it doesn't seem practical to me to have all of a group's code in one repo, but in different branches - it feels like it's fighting the git data model. (And to your closing point, it certainly feels like it's fighting the GitHub UI.)
This might be me misunderstanding how your large svn repo was arranged, though. Could you describe that further?
This might be me misunderstanding how your large svn repo was arranged, though. Could you describe that further?