Changes in codespaces are not showing up in the clone of repo

[GcalGit93]

Select Topic Area

Question

Body

Hello,

I'm very new using Git and Github, so forgive me in advance if I am not being the most clear with the terminology.

I recently made a codespace from a repo created by someone else to follow a script from a coding tutorial. In the codespace, I changed some files and added some code as part of some exercises as well as some comments which I now want to save to a local clone of the repository.

I first forked the repo as it sounded like if I wanted to save those changes in my own account, doing so would be one method. When I create a codespace from the forked repo, I do see the changes I originally made. I read that i needed to commit all changes in order for the repo to be updated, and so I did that within codespaces, and that is where I stopped doing anything else in codespaces (it sounds like I may need to publish as well...? but that runs into issues as well...)

The problem comes when I try to clone the forked repo. The committed changes in codespace does not make it into the local copy that appears on my desktop.

Can someone advise on how to clone the forked repo with all the changes made in codespace?

[JonathanZawadke]

What issue does appear? Do you get an error?
after you commit you ned to publish / push you can do that with:
git push origin main
this uploads the commits to github

[GcalGit93]

I actually do get an error. This is the output after running git push in the codespace's

Enumerating objects: 45, done.
Counting objects: 100% (45/45), done.
Delta compression using up to 2 threads
Compressing objects: 100% (34/34), done.
Writing objects: 100% (43/43), 29.86 MiB | 5.67 MiB/s, done.
Total 43 (delta 7), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (7/7), completed with 1 local object.
remote: error: Trace: 481ff1b945aad638a074bd50e4f51346919cd4f712edefec3bb16572b1b2e389
remote: error: See https://gh.io/lfs for more information.
remote: error: File mlruns/0/7f38f3813a45471b9e44c9522f08e42e/artifacts/rf_pipe/model.pkl is 144.83 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
To https://github.com/GcalGit93/applied-machine-learning-foundations-3856104.git
! [remote rejected] main -> main (pre-receive hook declined)
error: failed to push some refs to 'https://github.com/GcalGit93/applied-machine-learning-foundations-3856104.git'

I only changed one text file and added several lines of code as well as comments on a python script. If the error is related to a file size, is there a way to just commit changes on the two files I edited?

[puspah-ghimire]

Hi, it sounds like your changes were committed inside the Codespace, but not yet pushed to your forked GitHub repo. That’s why you don’t see them when cloning locally.

To fix this:
In your Codespace, open the terminal.
Run: git push
This will push your committed changes to your forked repo on GitHub.

Then, on your local machine:
If you already cloned the repo, run:
git pull

If not, clone it using:
git clone https://github.com/your-username/your-forked-repo.git

[GcalGit93]

Hi thanks for the advice. I am running into an issue running git push in codespaces. Here is the output of the terminal:

Enumerating objects: 45, done.
Counting objects: 100% (45/45), done.
Delta compression using up to 2 threads
Compressing objects: 100% (34/34), done.
Writing objects: 100% (43/43), 29.86 MiB | 5.67 MiB/s, done.
Total 43 (delta 7), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (7/7), completed with 1 local object.
remote: error: Trace: 481ff1b945aad638a074bd50e4f51346919cd4f712edefec3bb16572b1b2e389
remote: error: See https://gh.io/lfs for more information.
remote: error: File mlruns/0/7f38f3813a45471b9e44c9522f08e42e/artifacts/rf_pipe/model.pkl is 144.83 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
To https://github.com/GcalGit93/applied-machine-learning-foundations-3856104.git
! [remote rejected] main -> main (pre-receive hook declined)
error: failed to push some refs to 'https://github.com/GcalGit93/applied-machine-learning-foundations-3856104.git'

There seems to be several things going wrong, not sure where to begin.

[prisha-11]

Hey I faced the same issue and I'm also still new to github.
But the thing is now i cannot open codespace as i have reached my free subscription of it so I cannot git push it from it's terminal.
So what can be done in this case?

[GustavoAlmeida-cy]

Cloning My Codespace Changes to a Local Repository

I'm very new to Git and GitHub, so I wanted to document the steps I followed to clone the changes I made in a GitHub Codespace to my local computer.

What I Did

I started by forking a repository that someone else created, and then I created a Codespace from that fork. I made changes in the Codespace — added some code, comments, and completed some exercises.

After finishing my work, I wanted to save those changes to my local machine by cloning the forked repository. However, I noticed that when I cloned the repo to my desktop, none of my changes showed up.

What I Learned

The reason my changes weren’t in the cloned repo is because I hadn’t pushed the commits from the Codespace to GitHub. Committing changes in a Codespace doesn’t automatically upload them to GitHub — I also need to push them.

Here’s what I did to fix it:

Step-by-Step Instructions

1. Make Sure All My Changes Were Committed in Codespace

In the Codespace terminal, I ran:

git add .
git commit -m "My changes from the tutorial"

2. Push My Changes to My GitHub Fork

To upload the changes to GitHub, I ran:

git push origin main

If I saw an error about no upstream branch, I used:

git push --set-upstream origin main

This pushed all my local changes from the Codespace into my forked repository on GitHub.

3. Clone the Forked Repo Locally

Now that my fork on GitHub had the changes, I could safely clone it to my computer:

git clone https://github.com/MY_USERNAME/MY_FORK_NAME.git

I replaced MY_USERNAME and MY_FORK_NAME with my actual GitHub username and the name of the forked repo.

Optional: Push to a Separate Branch

If I didn’t want to put my changes directly on the main branch, I could’ve used:

git checkout -b my-changes
git push origin my-changes

Final Check

I double-checked my fork on GitHub and confirmed that my files and commits were there. Then, cloning worked as expected.

---

Hopefully this helps me or others if I ever run into the same issue again!

[GcalGit93]

Thanks for this! I am running into this issue. I think it might have something to do with permissions on the original repo before I forked it? Here is the output of git push origin main:

Enumerating objects: 45, done.
Counting objects: 100% (45/45), done.
Delta compression using up to 2 threads
Compressing objects: 100% (34/34), done.
Writing objects: 100% (43/43), 29.86 MiB | 5.67 MiB/s, done.
Total 43 (delta 7), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (7/7), completed with 1 local object.
remote: error: Trace: 481ff1b945aad638a074bd50e4f51346919cd4f712edefec3bb16572b1b2e389
remote: error: See https://gh.io/lfs for more information.
remote: error: File mlruns/0/7f38f3813a45471b9e44c9522f08e42e/artifacts/rf_pipe/model.pkl is 144.83 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
To https://github.com/GcalGit93/applied-machine-learning-foundations-3856104.git
! [remote rejected] main -> main (pre-receive hook declined)
error: failed to push some refs to 'https://github.com/GcalGit93/applied-machine-learning-foundations-3856104.git'

[GcalGit93]

Hi all. I figured out my issue. I de-committed the pkl file listed in the error seen in my replies. It was easiest just to remove the file as it was a file that the code generated. I was able to then commit and push my changes to the fork which made it into my clone. Thanks everyone that clarified the process!