Feature request: student/team repos should not be forks

[jennirinker]

Hi everyone,

I came across a serious issue today that is almost a show-stopper for me with GitHub Classroom.

I want student repos to be Private for a few weeks while they are working on projects, then I want to change them to Public once the deadline has passed so that students can do peer review. However, since the team repos are forks off a base repo (which is itself a fork off a template repo...why!?), I am not allowed to change project visibility for security reasons.

I don't see why the team repos should be forks of the base repo. I can't image a situation where I want a PR from one of the students to the template repo. So why on earth is there a fork relationship with the student repos?

[ebndev]

Hi @jennirinker, thanks for posting in GitHub Discussions!

I've gone ahead and moved this post to our Repositories category, as this topic has to do with overall repo visibility and that might help someone give you a nudge in the right direction 😄

[jennirinker]

Okay, thank you!

[Aravindhan-KS]

Hi @jennirinker

I believe we can add contributors to private repo ( My mate and I decided to create a project made the repo private and gave him contributor access , he actually hasn't done any work on it , I have no idea what contributors do to a repo tho)

[jennirinker]

Yes, of course one can manually grant or remove people to a repo. But that's not what I want to do, because then I would need to add my entire class roster to every single class repo. It would be much easier to be able to change the repo privacy settings as needed. But this cannot be done with active forked relationships.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐