I believe I am encountering a similar problem. Apologies if I am reviving a topic that was meant to stay dead and buried…
I released an assignment today via a GitHub Classroom invitation link. Out of 50+ students, one somehow ended up with an empty repository after accepting the assignment.
After reading a couple of issue threads related to this problem, I decided to delete his empty repository and have him once again accept the assignment. Unfortunately, the invitation link redirects him to a non-existent repository. My next attempt at solving this was to create an empty repo with the proper assignment name (
assignment-prefix-studentghusername), add it as a remote to the source repo for the assignment, push to it, and provide the student with write access to the new repo. This works in that the student is able to access the assignment, but it does not appear in the list of student repos associated with the assignment.
My guess is that once the due date has passed and I clone all student repos for this assignment via the app, his will not be among those gathered via the GitHub Classroom Assistant app. Luckily, only one student ran into this error.
I would just like to know if there is a better way to handle (or avoid) this error in the future. For example, can I resolve it via some API call? From what I’ve read, template repos may be one solution to this problem (can any repo serve as a template repo, or are there structural restrictions?).
Are template repos the answer or has this kind of issue been encountered even with assignments utilizing template repositories?