Visibility for Organization Repo


(Philip R. Ventura, Ph.D.) #1

Originally I created a organization repo that contains the code I show in class. I create a new directory there for each class meeting. Recently, I turned the organization into a classroom to have students work on group assignments. I have created the first group assignment and GitHub Classroom said “The GitHub “Default repository permission” must be set to “None” to ensure full privacy of group assignment repositories,” which I did since I did not want the student groups to be able to view each others’ code.

The problem is that this seems to be preventing students from viewing the lecture code repo. I want the lecture code repo only viewable to organization members. When I look at the visibility settings, there seems to only be private and public options. My understanding is that public will allow anyone to view it, including those not in the organization. So how can I set it to allow only the students to view it?


(Mark Tareshawty) #2

Hi @drpventura

Just to make sure I have the full context, is the lecture code part of the assignment for each student?

If that is the case then, you can make your assignment private and give your assignment starter code.

This will make sure that only the students who access to the assignment can see the lecture code.

If this is not what you were looking for, please let me know.

Thanks!


(Philip R. Ventura, Ph.D.) #3

Originally, I did not have an assignment created for the Lecture Code. However, just yesterday I created that. However, a few questions have arisen. First, as my LectureCode repo is being updated each week with a new folder for each day of lecture, will the students automatically see the new folders in the repo as an assignment?

Also, I usually provide a link in our LMS directly to the correct directory in the LectureCode repo. I suspect, however, that will not work using this method?


(Jaime Chavarriaga) #4

Because Classroom creates a fork for each student, I think the changes are not replicated automatically. The students must perform a “pull” to get the changes.

Here, some ideas…

  • You can make public the lectures’ repository.
  • You can use Gitbook or Jekyll to publish the lectures using Github-pages. The lectures will be public, even if the source code is private.
  • You can create a group with all your students and give them permissions to the lectures’ repository

(Rob Muhlestein) #5

Once again, really important to understand invite-accepted, student classroom assignment repos are imported not forked.


(Mark Tareshawty) #6

That is correct, if we forked the starter code any student with access to a fork would be able to see the entire network for forks.