Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cloning student repositories not working

Open
#104 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
git, github, go
Domain
cli

Research direction

Start with the gh classroom clone student-repos command and its assignment-listing and repository-cloning entry points. Reproduce the behavior in WSL2 with the reported classrooms, then compare the assignments returned with those visible in GitHub. Done means all assignments are listed and selecting one clones its student repositories.

Written by the indexing model from the issue text.

Description

I am having problems with "gh classroom clone student-repos". I am using it in WSL2 with Ubuntu-22.04. In the past, I have used this without problem, but something changed.

In one of the courses, it says there are no assignments:
"2025/06/10 17:50:43 No assignments found for this classroom."
However, there are six assignments, all created between in September and December 2024.

In another course, it shows me 15 assignments from several years, but not the most recent one.

In addition, when I select a specific assignment, it tells me this:

"? Select a classroom: my course
? Select an assignment: the assignment name
Creating directory: /home/me/mycourse/-submissions
Cloned 0 repos."

If I use the assignment flag, the result is the same.

Despite this, I am still able to clone each of the student repositories individually (git clone ...), even for the assignment not shown by "gh classroom clone student-repos".

I have uninstalled and re-installed gh, including the extension, but the result doesn't change.

Any idea how to handle this?

Dominant language
Go
Stars
126
Forks
21
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/gh-classroom

All issues in github/gh-classroom

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.