Ahh, sorry. By “project”, I mean something like “github.com/RiceComp215”, which is where all my student repos go, via GitHub Classroom, versus “github.com/RiceComp215Private” (or equivalent), which is where I have things I don’t want my graders to see, which includes my slides, my plagiarism writeups for the university’s Honor Council, etc.
Basically, within my RiceComp215 project, my graders are all “owners”, which means they can see everything there. Elsewhere, they’re not, so I can more easily do access controls.
Likewise, if you want your students to all see things, you can make them members of your class “project” (again, e.g., “RiceComp215”) or just make them all a “team” where that team has read-access to whatever shared repo you want.
The hard part is pushing changes out to the students. I guess you could script things up to push changes to each and every student repo, but they’ll have to pull from the repo to get your changes, and if they continue onward without that pull, you’ll have merge conflicts to explain. I’m just crossing my fingers and hoping I never have to do this.