You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 24, 2024. It is now read-only.
Describe the bug
During the automated creation of GitHub-classroom repositories for group assignments, one teacher (maintainer) is randomly added to each created GitHub team.
Actual behavior:
One teacher is randomly added to each of the created teams, so that for example I ended up being added to 4 teams (see screenshot below).
Anyway, if the behavior I described above is not a bug but the (new) expected behavior, as per the principle of least surprise I believe it'd be more natural to be able to customize this as an opt-in(?)
Additional context
I don't know if this is related, maybe not, so in this case please ignore that last remark:
during the session, one student was not able to join a team https://github.com/orgs/M2DL/teams/gmt through GitHub Classroom: when he clicked on "Join" an error message was triggered (we didn't make a screenshot of that, sorry)… so I had to add him manually in https://github.com/orgs/M2DL/teams/gmt/members
The text was updated successfully, but these errors were encountered:
Unfortunately due to technical limitations of how GitHub Classroom is built at the moment, this has to be done. We're looking into possible ways to solve this sometime in the future though.
But beyond the fact the current behavior is not intuitive, are you sure this couldn't also trigger an issue regarding the maximum-number-of-members-per-team if one select that constraint in the group assignment?
(as I said in my initial post, I had to manually add one student in a given group as he didn't manage to join this group by the invitation link… but I guess this could be an unrelated transient issue as this had not been experienced by other groups)
The maximum-number-of-members-per-team limit doesn't look at the number of people in the GitHub.com team, it uses an internal GitHub Classroom counter, so it should be unaffected. The issue you had sounds like it may have been a transient issue, please let us know if this happens again!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
During the automated creation of GitHub-classroom repositories for group assignments, one teacher (maintainer) is randomly added to each created GitHub team.
Cc @jochy FYI
To Reproduce
Steps to reproduce the behavior:
https://github.com/GHOrgName
)https://classroom.github.com/g/XXXXXXXX
)https://github.com/orgs/GHOrgName/teams
Screenshot of the GitHub classroom configuration
Expected behavior
The members of the teams match those of the group-assignment in https://classroom.github.com/classrooms/
Actual behavior:
One teacher is randomly added to each of the created teams, so that for example I ended up being added to 4 teams (see screenshot below).
Screenshots
in the particular case of:
Anyway, if the behavior I described above is not a bug but the (new) expected behavior, as per the principle of least surprise I believe it'd be more natural to be able to customize this as an opt-in(?)
Additional context
I don't know if this is related, maybe not, so in this case please ignore that last remark:
during the session, one student was not able to join a team https://github.com/orgs/M2DL/teams/gmt through GitHub Classroom: when he clicked on "Join" an error message was triggered (we didn't make a screenshot of that, sorry)… so I had to add him manually in https://github.com/orgs/M2DL/teams/gmt/members
The text was updated successfully, but these errors were encountered: