I’m having an issue with the GitHub client for Windows. I’ve been frequently committing changes to my branch named ‘modeling-users’. Recently, I noticed that not all of my latest commits are visible in the commit history for this branch when I check it in the application. However, when I open the terminal and run the command git log, all of my commits are listed as expected. I also checked the GitHub website, and it shows the same incomplete history. I’m puzzled as to why my commits are not appearing in the history. Can anyone explain what might be going wrong?
Had the same thing happen - commits showed up locally but disappeared from GitHub. One thing nobody’s mentioned: you might’ve force-pushed or rebased at some point, which rewrites commit history. Check if a teammate force-pushed to the same branch - that’ll overwrite your commits on the remote even though they’re still in your local git log. Also make sure you’re looking at the right branch on GitHub’s web interface. The default branch view doesn’t always show what you expect. Run git log --oneline origin/modeling-users to see what commits actually exist on the remote version of your branch, then compare with your local git log --oneline. If they don’t match, you’ll need to push your missing commits again.
This scenario happened to me last month. It was a syncing issue between my local repository and GitHub. While the commits are visible in the git log locally, it’s likely they weren’t pushed to the remote repository correctly. Start by running git status to see if your branch is ahead of the remote. If it is, use git push origin modeling-users to push your branch. Sometimes, GitHub Desktop fails to push automatically, especially after network interruptions. After pushing, refresh both the desktop app and the GitHub website to check if the missing commits show up. If they’re still absent, ensure that you didn’t inadvertently make the commits on a different local branch with a similar name.
I’ve hit this before with multiple remotes. First, run git branch -vv to check which remote your modeling-users branch is actually tracking. The GitHub Windows client sometimes gets confused about upstream tracking, especially if you cloned from one remote but need to push to another. Your commits might exist locally but the push failed silently due to auth issues or repo permissions. Try git push --verbose origin modeling-users to see what’s actually happening during the push - it’ll show any errors the GUI is hiding.
Check your commit author settings in GitHub Desktop. I had the same problem when my local git config used different emails for different projects. If your commit email doesn’t match your GitHub account or isn’t verified, GitHub won’t show those commits on the web. Run git config user.email to see what email you’re using for commits, then check if it matches the verified emails in your GitHub settings. The commits show up in git log but GitHub filters them based on author verification. To fix it: update your git config with your verified GitHub email, then use git commit --amend --reset-author to fix recent commits if needed.
check if you accidentally committed in detached HEAD state - that’d explain why git log shows them but they’re missing from branch history. Run git reflog to see all recent commits and their refs. If that’s what happened, checkout your branch and cherry-pick those commits back.