GitHub Classroom: Creating Assignment Repositories with Forks Beta Update #127455
Replies: 19 comments 6 replies
-
Thank you for swift action to remedy the difficulties faced |
Beta Was this translation helpful? Give feedback.
-
My classroom, which is opted into the beta, is having an issue where workflow actions that are part of the template are not showing up in the student repos as runnable. If they edit the .github/workflows/___.yml file, even just adding a space, the workflow shows up in the list of runnable actions. |
Beta Was this translation helpful? Give feedback.
-
Question?? I checked visibility settings/commits all look good. but still facing that error |
Beta Was this translation helpful? Give feedback.
-
why is it that after forking the repository i cant stiil push is there i way the accees can be chnaged in that students can easily submit or commit their |
Beta Was this translation helpful? Give feedback.
-
Thank you! |
Beta Was this translation helpful? Give feedback.
-
This is all great...but given that we're back to template repositories to a certain degree, would it be at all possible to provide the ability to have starter code from another private organization? This was removed a number of years ago so now my workflow is this.... Maintain a gold copy of my assignment in a non-classroom organization Could it be possible to be able to use starter code from another private organization that I also own like before so that at least I only have one repository in the classroom repo instead of two? Thanks, |
Beta Was this translation helpful? Give feedback.
-
Hello dear community! Thanks, |
Beta Was this translation helpful? Give feedback.
-
In my opinion, this is a clumsy step in the wrong direction. I have a curriculum org, with assignments and solutions in private template repos; I then create an org for each cohort of students I teach. When I create a student assignment, I first create a new repo (from one of the templates in the curriculum org) in the student-cohort-specific org, make the new repo a template, and then use that as the starter repo for the assignment. I opted in to the new assignment system (with forked student repos) last month; as of one week ago, all of the above was still working fine. But yesterday when I did this, another repo was then unnecessarily created in the student cohort org (as described above in the update post), with a crazy long name (created from the concatenation of a slugified form of the descriptive name of the student cohort org, the name of the repository that I specified as the source, and the name of the assignment), and that unnecessary repo is used as the started repo for the student assignments. This is all as described above—and it's ridiculous. If this is the way this will work, why not go back to what we had a couple years back, where we could select a private template repo from another org as the assignment source? The classroom bot could then create a source repo in the student cohort org from that curriculum org template, and student forks could come from that source repo; at least that would eliminate the duplicated repos in the student cohort org. Is there utility in having student assignment repos be created automatically as forks of the source org? Of course. However, there are many cases where that is overkill, and creating a student repo from a template (but not as a fork) is entirely sufficient; in working around some of the obvious potential issues with making the student repos forks of the source org, this latest update seems to be a kludgy acknowledgment of this, while complicating the situation for all GitHub Classroom assignment creators. |
Beta Was this translation helpful? Give feedback.
-
Help! I have read the updated instructions. I have been using the new system since June 1. Everything worked for me a few days ago (after the change to the system making a COPY of my template to use as the starter code from which to fork). When I went to create a new assignment Friday, it failed with the message "Starter code repo could not be copied to your organization". That behavior continues today. As a temporary workaround, I reverted my classroom to the old system. (I then had to change all my starter repos previously created to be templates, for the sake of students who are behind.) But if this problem is not fixed before the final rollout, it will be a disaster for me. *** I STRONGLY RECOMMEND DELAYING the July 1 rollout until adequate testing of the system has been done. *** Edit June 29: The new system seems to be working for me now. As others have noted:
|
Beta Was this translation helpful? Give feedback.
-
One new bug I've seen (wasn't present last week, but present today) is when I create team assignments, all teams are given |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Hi everyone,
Thank you to all the teachers who opted in to the Public Beta for creating student repositories with forks! Your feedback has been invaluable as we decide on our path forwards.
In our feedback survey, you told us how useful being able to update student assignments is to your workflows.
However, you also told us your frustrations with setting up your assignments in light of some of the important changes we shared in our beta announcement, particularly:
We have planned changes to address these (and more) concerns brought to our attention during the Beta. You might see these changes as they're implemented if you're opted in to the Beta:
These changes will start rolling out to current Beta participants in the coming weeks. We anticipate generally rolling out these changes (and moving everybody to the new assignment repository creation strategy) on July 1, 2024.
Thanks again for all your feedback! I'm heading out of office tomorrow, but will be back on the 19th to answer any questions you all have!
Beta Was this translation helpful? Give feedback.
All reactions