We found that communication in newsletters and in the Classroom UI has not reached all teachers and thus posting an update here about key changes and actions you need to take when using starter code in Classroom. Going forward you can find communication on Classroom changes in GitHub.com Changelog. This won’t be normal practice in the future unless y’all prefer it to be that way.
Important information about the change and what you need to do
In October we made a change to GitHub Classroom that changed some things about starter code. You need to have your starter code:
- Within the organization associated with your Classroom - it can be private or public in this case, depending on your preference
- Outside of the organization associated with your Classroom - it has to be public and can no longer be private
If your starter code is outside the organisation, it means that you need to transfer 2 or fork 4 your repository to your Classroom organization for your assignment to work properly if you want to keep it private. If you are comfortable making the repository public you can keep it outside of your organization.
If you have an assignment created before Oct 2020 that is set up in this way it will not work and the students will see an error. You will need to move your starter code or make it public and then edit your assignment.
If your classroom organization is on our Standard Terms of Service agreement this does not change the ownership of the contents of your repository in any way by moving it to the organization.
Some context on why:
This was an internal ask from our Security team at GitHub as we transitioned away from the old architecture of GH Classroom. As of last summer GH Classroom was built in a way that just wasn’t scaling with how folks were using it and how we wanted to grow the product. We want to provide you with more stable features that better integrate better with .com so we started a large project to make those backend improvements. This change opens up the door to features like public APIs, configurable assignment YAML files on .com, and a more stable assignment acceptance process (just to name a few!)
Our apologies for this seeming like an abrupt change. We chose to do this during a downtime of assignment creation and acceptance in October and included some warnings in the UI of Classroom as well as a callout in the teacher newsletter.
Going forward we can find about all Classroom changes in the GitHub Changelog.We also plan on adopting an opt-in and beta model for our bigger features to ensure you don’t get surprised during the semester.
My inbox is open for feedback and i’d love to hear from you on this thread or vie email if you want to share pain points around this flow, more general feedback about GH Classroom, or just have questions. We are trying to improve your workflow, not harm it, so we are always open to alternative solutions (that our Security team approves of ).
Sorry for the long windedness, but I appreciate you reading til the end!