Repository navigation
SOLVED: Workaround for the broken "Start Course" automation (stuck on Setup) #1208
Unanswered
itamarassaf-TAU
asked this question in
Code with Copilot
Replies: 6 comments
|
This fix worked for me, thank you very much! |
0 replies
|
I had same problem it wrok's now thanks. |
0 replies
|
Thank you so much for the help! |
0 replies
|
Thank you It worked for me! |
0 replies
|
Bro, you are the real heeeeeero! |
0 replies
|
This worked! Thank you! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Found a solution. The guide relies on the "Start Course" button automatically pushing the fork's content to your new repo, but the automation seems broken—it tells you to wait 20 seconds, but nothing happens.
The Fix: You have to manually push the code yourself.
Clone your forked repository to your computer.
Push that code into the new repository you created.
Here are the commands to do it:
Bash
1. Clone your FORK to your computer
git clone https://github.com/YOUR-USERNAME/forked-repo-name.git
cd forked-repo-name
2. Link it to your NEW repository (replace URL with your new repo)
git remote set-url origin https://github.com/YOUR-USERNAME/new-repo-name.git
3. Push the code
git push -u origin main
Once you do this, the course triggers correctly.
GitHub, you should probably pay me for this.
All reactions