Private forks created by Classroom don't have actions enabled #102536
Replies: 3 comments 1 reply
-
Same problem here. When the students accepts the assignment, the tests are not added with Github Classroom Bot in the Student's forked repository. Also the same @mainland problem in the Student's repository after forks, because Actions is not enabled by default. |
Beta Was this translation helpful? Give feedback.
-
In my case, my student accounts don't see a "Sync Fork" button when I update the base code or README file. They have to go through the multiple clicks of a pull request and merge. This wouldn't be so problematic if it weren't a high school class who are completely new to GitHub (and programming). |
Beta Was this translation helpful? Give feedback.
-
Hi @mainland 👋 We have an active discussion regarding this topic (enabling workflows on student forked repos). You can see the latest updates and share your experiences here. 👈 |
Beta Was this translation helpful? Give feedback.
-
Hi everyone,
I have switched to using the new forking method with Classroom. The sync functionality is great for making sure students can easily get assignment updates, but there is a big downside: private repository forks have actions disabled by default. I use GitHub actions to run a test suite every time a student pushes to their repository, but with the new fork model, this doesn't happen.
Even worse, there is no way to enable actions on a forked repository using the REST API. This means I have to manually click on hundreds of repositories to enable actions.
Yes, I know it looks like the REST API provides this functionality, but it does not. Maybe the REST API hasn't yet caught up to the new multiple-forks-in-org feature.
Could Classroom automatically enable actions on private forks?
Beta Was this translation helpful? Give feedback.
All reactions