We found the issue: there was a change in the format of a local storage value between 1.63 and 1.64, in the SCM feature area. When github.dev bumped VS Code to 1.64, users got that value format migrated. Unfortunately, 1.64 had more serious issues so github.dev rolled back to 1.63 until 1.64 gets fixed. This new format is not compatible with 1.63, so everything breaks down. This means that only users who opened github.dev/vscode.dev in the short window that 1.64 was out are affected. And only in the repos that they opened then. The good news is that a new 1.64 release is almost out and github.dev should update to it asap, and this issue will get resolved.
In the meantime I suggest the following workarounds: Clear browser storage or use a different browser.
Why I am not able to commit any repository in github? - Stack Overflow
git - commits not showing up on github - Stack Overflow
Can't commit changes in github desktop
git - not be able to commit and push a project to GitHub - Stack Overflow
I found solution for this problem: Problem is occurring due to I Added extension in chrome i.e. ad blocker extension. So, I removed that extension and problem is solved.
Make sure you have modified/updated any contents in the README.md file. If there is no changes in the file, "Commit Changes" but will be disabled.
After your Github repository has been created (i.e. you can view it on Github), then you should already have:
1. Local repository set up:
git init
2. README file created and added to the repository:
touch README.md
git add README.md
git commit -m 'first commit'
3. A remote called origin linked to your repository:
git remote add origin https://github.com/username/repo.git
4. An initial push, which copied your local README to your Github repository:
git push -u origin master
If you can view your repository on Github, then it has been successfully created. In this case it looks like you may have edited your README file on Github using the online editing tools, which caused your remote and local branches to diverge.
Before you can push your local changes to Github, you need to fetch or pull your remote changes, merge the changes locally (merging is automatic with pull), and then push to the remote.
See Pro Git: Fetching and Pulling from Your Remotes
When you created the repository on GitHub you selected initializes remotely containing a README.md file. The next step would be to run git clone https://github.com/username/repo.git in your terminal. At this point you have a local copy on the GitHub repository, so you would then move in your project files. Run git add * then git commit -m 'first commit' then git push origin master. Your changes should now be visible on GitHub.
Using git through a GUI usually adds confusion instead of being helpful. One should try to get the git basics right in the first place.
A normal routine should be the following:
1. Clone project
2. Checkout a working branch
3. Make changes
4. Commit changes
5. Push changes
This routine is usually expanded and is cyclic like so:
1. Clone project
# for each new activity
2. Checkout a working branch
# each day
2b. Git fetch // will get new content from remote, updates you on what your colleagues are doing
3. Make changes
4. Commit changes
5. Push changes
It appears in your case you didn't do at least one of these steps.
Please note that "uploading manually files on GitHub" is jargon for: "create new commit with a specified commit message and the files added to the staging area via GitHub GUI, sign off the commit with the GitHub user name and email".
This is important, since on your local machine you'll have to git pull, otherwise you'll be creating commits on a diverging history.
This should be an explanation on "what to do" and "how you get in your situation in the first place". It is probably out of scope to add more details in this answer, but please do let me know in the comments.
You need to go to to Settings -> Extensions -> Git -> Post Commit Command, and choose "push" from the dropdown.
Only then clicking the tick (commit) will trigger a push automatically.
By default, committing would remain a local operation.
I'm trying to push my code to a remote repository but every time I use git commit and git push it tells me "everything up to date" but the repository lacks the code. It shows the directories and files but not the code. Why is that?
I wrote to the GitHub team and this is what they had to say.
It looks like you're running into an out of memory exception: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. Unfortunately GitHub Desktop does have some edge cases that can cause an OoM -- mainly when working with a large amounts of commits or larger files. We're working on fixing performance to reduce these edges cases, but in the meantime I would try committing directly from the Git Shell:
- Hit ~ to open up the repository in the Git Shell
- Run 'git add -A' to stage the changes
- Run 'git commit -m "your commit message here"' to commit the changes
I haven't faced the problem again after I updated the desktop app(3.0.9.0 now).
I am seeing something similar when I "push" the changes to the remote (GitHub) after I upgraded to Windows 10 it seems to hang. It is like the "GitHub Desktop" application never comes back to confirm the push, but if I close the application and then open it again I can see that the "push" did happen at the time when I pressed the Sync button.
When I use the GitBash it works fine and fast. If I had the GitHub Desktop application running while doing this push from GitBash and now do a Sync the changes show up fast in the GitHub Desktop application but it keeps "Syncing" forever.