GitHub Classroom: Students unable to access classroom-created repositories immediately after creation

[frizensami]

Hi everyone,

Students in my class are accepting assignments and a good portion of them are being told that they cannot access the repository.

When I go to their repository settings and check their access , their user is "pending invite", but none of them can accept the invite.

Only removing their access, and then re-inviting them manually myself, solves the problem (they can then accept the invite).

This isn't a user error or something on my part as far as I can tell. I've run three successful assignments already over the past couple of weeks and this has the same setup.

For reference, my classroom ID is 845574

[jameswinegar]

Similar issue. I believe my classroom ID is 97207053. Link

[Chiru7711]

You're navigating a gnarly glitch in GitHub Classroom where "pending invite" lingers—and students can’t accept it unless you manually re-invite them. Let’s turbocharge your solution with razor-sharp innovation.

What's Behind the Glitch?

You're not alone. As of September 2025, multiple educators report the same "pending invite" hang-up in GitHub Classroom. Even though previous assignments went smoothly, new ones get stuck in limbo—only fixed by manual re-invites. Community posts confirm this as a systemic issue, not user error.
GitHub
+1

A credible workaround via the GitHub CLI has emerged: delete the pending invite via API and then recreate it.
GitHub

Command-Line Wizardry: Fast, Elegant, Repeatable

Here’s a slick way to automate your workaround—slash manual rehits, scale seamlessly:

`#!/bin/bash

Define your org and repo naming pattern

ORG_NAME="your-org"
PREFIX="assignment-prefix"

List assignment repos and reset invites

gh repo list "$ORG_NAME" --limit 1000 --json name
| jq -r '.[].name | select(startswith("'"$PREFIX"'"))'
| while read repo; do
full="$ORG_NAME/$repo"
gh api "repos/$full/invitations" --jq '.[] | "(.id),(.invitee.login)"'
| while IFS=',' read id user; do
echo "Revoking invite for $user in $repo"
gh api "repos/$full/invitations/$id" -X DELETE --silent
echo "Re-inviting $user"
gh api "repos/$full/collaborators/$user" -X PUT -f permission=write --silent
done
done
`

[fchsLemke]

Hey, I figured I could give something a little more helpful than this AI-generated response. Hopefully a little humanity goes a long way, since I don't expect most CS teachers (at least at the high school level) are used to writing or reading shell scripts. I'm also going to assume most of you are on Windows since that's what most school corporations use. If not, you'll likely need to make some modifications here. I don't live in the command line, so I just have to hack through it. This is what I got to work:

First, if you haven't used PowerShell before, open it and type in "winget" to see if it gives you an error message. If it doesn't, then you can run the following commands to make sure you have all of the tools you need:
winget install -e --id GitHub.cli
winget install -e --id jqlang.jq

EDIT: If you haven't used the Github.cli before, it will ask you to login. I don't recall all the steps, but you'll probably want to choose HTTPS and then something like "login through a web page" or something like that for the easiest experience.

The script above assumes you have these packages, but you very well might not. If winget doesn't work for you, you can try installing these tools manually, or you can follow Microsoft's instructions for installing winget.

Now you can run the following script AFTER you replace "CentralHighSchool" with the name of your Github Organization and "project-01" with the name of your assignment repo prefix.

# uses github's cli to get all the repos from your org (replace 1000 if you have more repositories than that)
gh repo list "CentralHighSchool" --limit 1000 --json name |
# narrow down your query to only those that start with your assignment name
jq -r '.[].name | select(startswith("project-01"))' |
while read -r repo; do
	full="CentralHighSchool/$repo";
	full="${full::-1}";
	# use github's api to get a list of invitations and extract the invite id and the username
	gh api "repos/$full/invitations" |
	jq '.[] | "\(.id),\(.invitee.login)"' |
	while IFS=',' read -r id user; do
		#use github's api to revoke the existing invite and send a new one
		echo "Revoking invite for ${user::-2} in $repo";
		gh api "repos/$full/invitations/${id:1}" -X DELETE --silent;
		echo "Re-inviting ${user::-2}";
		gh api "repos/$full/collaborators/${user::-2}" -X PUT -f permission=write --silent;
	done;
done;

Is this the most beautiful way to do this? No. Again, I'm not a command line expert. I only know enough to be a danger to myself.
I also haven't checked if this fixes the access issues for my students because I'm in Eastern US Time, so they're already gone for the day.

Good luck to anyone else that fumbles across this issue. Hopefully this helps someone. (Hopefully this helps me!)

[fchsLemke]

I confirmed with my students today that this did work for them. The only catch is that if any students accept the assignment AFTER you send the new invites, you'll have to run this script again. It did work though and doesn't require you to host any services if that's a nonstarter for you.

[emil-freme]

Hey folks, and @fchsLemke thanks a lot for sharing your script!
Since I couldn’t get jqlang.jq installed, I put together two alternatives.
One for PowerShell and another in Python to make it more cross-platform.

I've tried to kept the GitHub CLI as the only requirement, as well as asking for the Org and Repo Prefix in the script to be more flexible.

https://gist.github.com/emil-freme/ead22d494e2db3ce4d1b22d9b638bec5

https://gist.github.com/emil-freme/a75c244b45433a7df62c7cf299a2303a

[ghostinhershell]

Hi @Chiru7711,

We’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team.  You can read our updated Code of Conduct and the announcement for more details.

Thank you for helping us maintain an authentic and beneficial space for everyone.

[SH-NicholasPage]

I am having the same issue with one of my students in one of my classrooms.

[jsgratch]

I am having the same issue with one student in my classroom ID: 76087654

[lycangeek]

Same issue - one student had no issue, multiple others are having trouble. Going directly to the per-student github repo directly and removing and adding them there (not via the classroom site) fixes the issue. Classroom ID: 167712693

[frizensami]

Yep, I've been doing this all of yesterday and today. The invites work for some, but not for others.

[NuttKatyISD]

Looks like a common issue - #72283

There's a script on that page that'll use gh to go through matching repositories and revoke any pending invitations and re-invite them. Seems to be work and much easier than doing it manually one at a time.

[djholt]

I've seen this a handful of times in the last 24 hours. I've just been deleting the repos to fix it, but it's a hassle.

[catherine-leung]

This is a new issue I think.. I use classroom extensively and this is the first semester where this has been a problem. The issue seems to be that a student's invitation is immediately revoked and invalidated. I think this is a bug on github's end...

Having said this, I do have a work around that is simpler than deletion but it's still a hassle

Go to the student's repo
Go to settings for the repo
Collaborators and Teams
Remove the student from the team
then add them again
Student gets a new invitation and when they accept it they are "fixed"

[jjgr29]

I am also having this issue with numerous students.

[jeffbcit]

I'm having the same issue.

There seems to be an in issue with the invitations becoming invalid as soon as they're accepted.

A workaround per student is to delete the exiting invite and send another invite manually.

1 - Go to their repository > Settings > Collaborators and Team.

2 - Then in the "Manage Access" area, delete the pending invite

3 - Once they're deleted, re-add them by pressing "Add People", enter their github id, and set their permissions on the next page

4 - You will return to the prior page, then click the two squares next to "pending invite" to copy the new invitation.

5 - Send this invitation to your student, after they accept, they should have access to the repo.

I hope this is fixed soon as I've been manually doing this for over 50 students. And I'll have to keep repeating this every week until it's fixed.

[brainark1]

I've also seen this issue - from playing around with the invite link, I've found that I can trigger it about 70% of the time if I wait for more than 15 seconds after following the invite link to click 'Accept Assignment'. I've been encouraging my students to click all the way through promptly, which has helped reduce the number that need a manual fix-up - I suspect students with slow internet connections may be switching tabs while they wait for the link to load, leading to slow click-through rates.

[uwf-fang]

I have the same issue in 4 assignments. There are more than 200 repositories created by students and about 20 of them have this problem.

I have tried three different ways so far.

1. Cancel the invitation and re-invite, students will receive an email and accept the invitation there
2. Make another duplicate assignment for students to accept
3. Delete the repository and let students to re-accept

All methods have the chance to work or not work. What I can do is just let student roll the dice and hope it will work well. I still have unlucky students who fails with all the three ways. I hope the team will fix this problem soon.

[liberty-bradleyd]

Unfortunately, I am experiencing this issue this year too. I have used Github Classroom for several years and not experienced this before. Out of my 150 students about 15-20% are experiencing the problem. I stumbled upon the manual fix of uninviting them and reinviting myself. I will try out the script above, if this occurs on the next assignment.

I do wonder if the root problem of github not thinking the student is part of the enterprise organization is due to me forking my base projects from my source organization. Up until late last year I used to import the repositories from my source organization into this year's organization, but that stopped working late in the school year last year.

[Ygilany]

Hi everyone 👋,

As many of you have likely experienced, there’s an issue across GitHub Classroom causing GitHub Classroom invitations to expire before students can accept them 😕. While we all hope GitHub resolves this soon, I built a temporary workaround that has already helped our students regain access quickly.

🔗 Example of the Hosted Tool: https://github-reinvite.vercel.app/
📂 Source Code: https://github.com/Ygilany/github-reinvite

How it works

Students who lost access to a Classroom-generated repository can:
1️⃣ Go to the site
2️⃣ Select their class and assignment (as you configure it)
3️⃣ Enter their GitHub username
4️⃣ Receive a fresh invitation instantly 🎯

For faculty, you'll need to host this application yourself using Vercel or anything you'd like: Fork the repo and run it on your own infrastructure 🌐

This is a community tool built in one night to help educators and students while we wait for a permanent fix from GitHub ❤️.

☕ If this helped you or your students, consider supporting the project: Buy me a coffee

Let’s keep our students coding without roadblocks! 💻✨

[skhattab]

Worked for me—thank you! To prevent abuse of the API, I made it return an error whenever no pending invitations exist for the specified user in the repository.

[Ygilany]

Since the issue is happening again.. I'm pumping this up again

[chenhan-fullsail]

The workaround is tedious but effective: I have to manually delete the affected repos and re-create them—sometimes more than once. Unfortunately, the most frustrating part is that I have to re-enter each repo name by hand. Please fix it asap! Thank you MS.

[Ygilany]

@chenhan-fullsail you only have to delete the invitation from the collaborator tab of the repo (not the entire repo), then you can invite the student again. You can do it manually, or:
https://github.com/orgs/community/discussions/171982#discussioncomment-14309367

[eblanton]

This problem is pernicious; I long for the days of yore when GitHub actually provided SOME kind of support for GitHub Classroom (although it has always been mediocre to poor).

I am currently using this script to fix the failed invitations, you are welcome to it if it works for you. Set the ORG variable at the top to your GitHub classroom organization, and run it as:

cycle-collaborator <assignment prefix> <github username>

For example, if you have configured GitHub Classroom to create repositories named assignment1-whatever-someuser, you would run cycle-collaborator assignment1-whatever someuser. You may then need to provide the invitation URL that it prints to your student.

If it breaks, you can have the broken parts for free. But unlike GitHub and GitHub Classroom, you also get the source, so you can fix it!

#!/bin/sh

GH=gh

ORG=

if ! jq -n . > /dev/null 2>&1; then
    echo "jq does not seem to be installed, cannot continue" 1>&2
    exit 1
fi

if ! gh help > /dev/null 2>&1; then
    echo "gh does not seem to be installed, cannot continue" 1>&2
    exit 1
fi

if ! gh auth status -a > /dev/null 2>&1; then
    echo "gh does not seem to be authenticated, please run \`gh auth\` and try again"
    exit 1
fi

if [ $# -ne 2 ]; then
    echo "usage: $0 <assignment prefix> <ubitname>" 1>&2
    exit 1
fi

PREFIX="$1"
GHUSER="$2"

GHREPO="$ORG/$PREFIX-$GHUSER"

checkexists() {
    $GH repo view "$1" > /dev/null 2>&1
}

if ! checkexists "$GHREPO"; then
    echo "error: Repository $GHREPO does not seem to be usable" 1>&2
    exit 1
fi

echo "Removing $GHUSER from $GHREPO"
echo "Checking for invitation first"
ID=`$GH api -XGET repos/$GHREPO/invitations | jq '.[] | select(.invitee.login == "'"$GHUSER"'").id'`

if [ "x$ID" != "x" ]; then
    if $GH api --silent -XDELETE "repos/$GHREPO/invitations/$ID"; then
        echo "Invitation deleted, moving on"
    else
        echo "Failed to delete invitation, aborting" 1>&2
        exit 1
    fi
else
    echo "No invitation found, trying to remove user entirely"
    if ! $GH api --silent -XDELETE "repos/$GHREPO/collaborators/$GHUSER"; then
        echo "Failed to remove $GHUSER from repository" 1>&2
        exit 1
    fi
fi

echo "Adding $GHUSER to $GHREPO as writer"
if ! $GH api --silent -XPUT "repos/$GHREPO/collaborators/$GHUSER" -f permission=write; then
    echo "Failed to add $GHUSER to repository" 1>&2
    exit 1
fi

echo "Done!"
echo
echo "User can accept https://github.com/$GHREPO/invitations now"

[ildarakhmetov]

this worked perfectly, thanks!

I just had to replace line 17 with if ! gh auth status -h github.com > /dev/null 2>&1; then (my gh is aware of github.com and another enterprise account which was not properly authenticated)

[kangwonlee]

@eblanton Thanks so much. I could resolve the issue with your help. 🙏🏻

[mattwilliamson13]

+1 for this problem. And some of these are for in-class assignments making the shell script workaround a less-than desirable option. Seems like something GitHub could fix?

[krohnrm]

Happening for me too. Deleting the repo didn't work for my student, but re-inviting them did. Hoping this gets fixed soon, because I have daily assignments and realistically can't keep using a workaround.

[jeffbcit]

I'm also having the issue. The most consistent fix I've found is to manually go to the student's repo, goto settings > collaborator's and teams > delete the existing invite, add back the student, copy the new invite link, and send it to the student for them to click

[fchsLemke]

If you have enough students that this solution ends up being a big time sink, you can try running the script in this comment. I saw a comment underneath saying they couldn't get jqlang to work, but it looks like it helped a couple people. There may be better solutions under this one, but I can only vouch for this one. Good luck!
https://github.com/orgs/community/discussions/171982#discussioncomment-14300306

[beak85]

When you add them back in as a collaborator, they will automatically get an invite to the repo in their github inbox. You shouldn't need to send to them. That should save you that last step!

…

________________________________ From: JeffBCIT ***@***.***> Sent: Wednesday, January 14, 2026 1:48 PM To: community/community ***@***.***> Cc: Matt Geiger ***@***.***>; Comment ***@***.***> Subject: Re: [community/community] GitHub Classroom: Students unable to access classroom-created repositories immediately after creation (Discussion #171982) I'm also having the issue. The most consistent fix I've found is to manually go to the student's repo, goto settings > collaborator's and teams > delete the existing invite, add back the student, copy the new invite link, and send it to the student for them to click — Reply to this email directly, view it on GitHub<#171982 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBZEBG64QCAGJSP67AZOGL4G2FRXAVCNFSM6AAAAACFL2PMACVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBZHEYDQOI>. You are receiving this because you commented.Message ID: ***@***.***>

[MaxRolseth]

What's worked for us, when they accept the invite that fails, it also sends an email to their GH account email, and the invite link in there has seemed to work for the time being. It's annoying to have the extra steps, but as long as you aren't having 10+ assignments per student per week, its an acceptable work around.

That way, its less for the instructor to do, which can be a LOT, especially in big classes.

[NuttKatyISD]

Popping up with our crew again over the last couple of days. What we're seeing is that the student is getting the invitation to join the repository but never actually connected, and they don't get the invitation email.

We've had luck with students going to https://github.com/settings/repositories and finding the assignment in the list and accepting the invitation there. Or, they can also go directly to the repository (link is next to their name in your Classroom list) and accept the invitation there.

[MaxRolseth]

What's worked for us, when they accept the invite that fails, it also sends an email to their GH account email, and the invite link in there has seemed to work for the time being. It's annoying to have the extra steps, but as long as you aren't having 10+ assignments per student per week, its an acceptable work around.

But I'm going to share this with our team too!

[catherine-leung]

After the trouble I had last semester doing this, I have gone to using "group" assignments. Instead of individual assignments, I create a "group" assignment with a maximum team size of 1 member. this does a few things:

• after the first assignment, students join the organization.. they are not external collaborators, thus every future assignment does not require invitation email
• for some reason, this process seems to be successful..they don't seem to be having the invitation issues that the individual assignments cause. Possibly because they are not outside collaborators so the invitation process is simpler? Not sure on this.. maybe I just prayed to the correct interweb gods this time.../shrug
• they do have to provide a team name. I have asked mine to use their email username. this puts whatever they type into the url. However, I have found that some don't follow instructions and use first/last name. truthfully this doesn't matter to me so I just let it be the thing they entered
• If you choose the same set of teams after the first assignment (where you have to put in a name for the group of teams), the students will automatically just get their repos without having to do the same thing each time.

This has been my work around and it has been pretty consistent.

[epignatelli]

It is worth mentioning that creating a group assignment to solve this will force GitHub Classroom to add students as Members of the organisation, rather than Outside Collaborators.

According to your base permissions, students might be able to see each other's repos.

[catherine-leung]

So, I was pretty certain but just did an experiment just now to verify.

When you first create a github organization the default permission is READ so all member can read everyone else's repo.

However, the moment you make a classroom and select the org for your classroom, it changes the base permissions to No Permissions.

Thus, unless you go and manually change it after, this should not be a problem.

[epignatelli]

Classroom clearly broke something, as students that recently accepted assignments are not automatically added as collaborators. Student that accepted the same assignment a month ago, were regularly added.

[Ygilany]

Since the issue is back again - pumping this up.

Hi everyone 👋,

As many of you have likely experienced, there’s an issue across GitHub Classroom causing GitHub Classroom invitations to expire before students can accept them 😕. While we all hope GitHub resolves this soon, I built a temporary workaround that has already helped our students regain access quickly.

🔗 Example of the Hosted Tool: https://github-reinvite.vercel.app/ 📂 Source Code: https://github.com/Ygilany/github-reinvite

How it works

Students who lost access to a Classroom-generated repository can: 1️⃣ Go to the site 2️⃣ Select their class and assignment (as you configure it) 3️⃣ Enter their GitHub username 4️⃣ Receive a fresh invitation instantly 🎯

For faculty, you'll need to host this application yourself using Vercel or anything you'd like: Fork the repo and run it on your own infrastructure 🌐

This is a community tool built in one night to help educators and students while we wait for a permanent fix from GitHub ❤️.

☕ If this helped you or your students, consider supporting the project: Buy me a coffee

Let’s keep our students coding without roadblocks! 💻✨

https://github.com/orgs/community/discussions/171982#discussioncomment-14309367

[Ygilany]

Also you can always ask your students to navigate to their repo by appending their username to the end of the repo name - they'll see another button to accept the invitation from there

for example for this assignment (campus-portal-js-exercises), I would need to go to campus-portal-js-exercises-Ygilany and accept the invitation from there since GitHub Classroom isn't able to accept the assignment for them.

[epignatelli]

@samus-aran Any news on the GitHub side? This is hitting right at the start of the term in the UK.

[epignatelli]

@samus-aran ?

[rameau-fr]

Last time it took them about 3 weeks to fix.
As my semester will start soon... I hope they will be able to fix it rapidly

[eringutbrod]

My students encountered this issue this week. They would accept their assignment and be taken to a page that says, "Repository Access Issue - You no longer have access to your assignment repository. Contact your teacher for support". Not every student had this issue. For anyone that encountered this problem, I told them to navigate to this page: https://github.com/settings/organizations
and as long as they were signed into their profile, it would offer another chance to accept the assignment and create the repo. This worked for everyone, it was a simple solution, and didn't require me to do anything.

[epignatelli]

Bummer! So far it's worked for all of my students. I wonder what the difference is... ?

No, not really! There might be some noise in there as some students might have not followed the instructions.

[tiagoasilva]

@eringutbrod Your suggestion worked for me. Thank you so much!

[g-pyxl]

Replied elsewhere but wanted to reiterate that this is the simplest solution I've came across so far that seems to work consistently. Thank you.

I have appended a small note to the class instructions to do this if they experience the repository access issue, then just use the assignment invite again, which seems to solve it.

[GitWithAlkeshShah]

I am still not able to get into the repo/organization

[artb83]

Worked for me as well - thanks a lot!

[h-arnold]

I can confirm this is still an issue. I tried it with my students today and after it working flawlessly back in June, they all ended up with this error.

[epignatelli]

The silence from the developers' side is really inappropriate for such a community, with such a product.

[eblanton]

It's been like this for years. Their automated verification system failed for me one year, and I never did get a resolution ... it just started working again, months later.

[chrissphinx]

@epignatelli ain't gonna be getting any better, either. It's pretty telling that they refuse to create a discussion board for GitHub Classroom instructors only and we have to chuck our threads into this endless pit of complaints about the Student Developer Pack verification process. I assume as a teacher in this era we're all very used to screaming into the void, though...

[ersheff]

This is rough. I've been using GitHub Classroom for a few years, but wasn't scheduled to teach any classes that used it in Fall 2025, so the first time I saw these errors was last week. I teach a lot of beginners in a non-CS department, and it feels like I've immediately lost their confidence in the platform and, to some extent, me as an instructor when I have to send out emails with workaround instructions.

GitHub was already kind of overkill for my classes, but I liked the Classroom setup and the ability for them to publish projects with Pages. It's too late to change midstream this semester, but now I'm thinking of ditching it next year.

[rameau-fr]

This is exactly my situation as well, and I hope they can address it quickly. The same thing happened last semester, and afterwards students started using it as an excuse to submit their code late, claiming that the platform was “unstable.”

[epignatelli]

I actually received a cold email suggesting an alternative to Classroom. I will post it as soon as I have a minute.

[AustenLamacraft]

Tell us!

[chenxofhit]

我在高级Web技术课上也碰到了这个问题, 创建了classroom后把classroom的link share出来后, 有些学生点击后得到的结果是404

[catherine-leung]

Check following:

• did repo get created? It will be named assignment-studentgithubid (for individual assignment) or assignment-teamname (for group assignment). If you find repo but in the settings of repo the student isn't there then they are not attached to the assessment.
• double check that students have accepted the invitation to your org.
• It can be fixed manually or there is a script in one of the forum posts in this thread that can do it on scale.

[chenxofhit]

After spending two hours with my student, we finally figured out the cause. During the classroom setup, I included a list of identifiers for student IDs and names. The student skipped the step of linking their name to their GitHub account after joining the classroom, causing a 404 error when trying to re-enter the classroom. Since the student was using a mobile phone, viewing this list on a phone wasn't ideal. The solution was rather crude: they registered a new GitHub account and repeated the process on a computer, which resolved the 404 error.

[robwhess]

Does anyone have any updates about the "Repository Access Issue" problem? My students are still running into this issue frequently, and it's kind of a pain. It'd be nice to know that a GitHub staff member is at least aware of this issue.

[robwhess]

Having all of my students create second GitHub accounts isn't really a viable solution to this problem. I don't believe that's the underlying issue here, anyway. Many of my students have correctly linked their names and are still running into this problem.

[robwhess]

I'm hoping a GitHub staff member could address this. A lot of people have weighed in on this thread, so this appears to be an issue a lot of people are facing. It's a little frustrating that no one from GitHub appears to have noticed.

[catherine-leung]

the linking of names to repo is an extra step only if you use the classlists feature I think. If you create the repo without this and have students submit the url of their repo (accepting that the url will be named after their user name, it kind of works better).

If you make an individual assessment, students never join the organization as they are outside collaborators. Each time you set another assignment they end up staying outside collaborator and so any issues regarding invitations remain and repeat. If you make it a group assignment (you can limit it to a team of 1 max), the students are added to the organization and I think that ends up skipping some of the issues because there is one less step (the invite to join repo step). Less moving pieces less issues. Note.. if you do group assignments, double check that the base permissions for org is set to None. This should be the default as soon as you create a classroom for an ORG but best to be sure. This will prevent students from seeing each others work.

[robwhess]

Thanks @catherine-leung, but I have several individual assignments in my classes before I have a group assignment. From my perspective, the bottom line is that this is something we shouldn't need to work around. It's an issue that should be fixed by GitHub staff.

[ssyberg]

I don't think it's a linking issue all my students are properly linked and it works very inconsistently.

[ssyberg]

Just noting my class this year is experiencing this a ton as well during every assignment/lab, it's quite disruptive. Never happened in previous years for us.