No Changes Seen After Pushing to Git. Git Internal Server Error [Closed]

Moderator Note: This error happens when GitHub has an outage or service degradation. We're leaving it up as a canonical post for others to see and close against as duplicates, but questions about service outages are off-topic.

There are similar questions but I could not find any answer that would solve the issue.

git status

On branch master
Your branch is ahead of 'origin/master' by 1 commit.
  (use "git push" to publish your local commits)

nothing to commit, working tree clean

I retract the local changes to the original state of last commit:

git reset --hard origin/master

Make sure it is up to date:

git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

Then make a small modification in the file.

git status

On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   test.py

no changes added to commit (use "git add" and/or "git commit -a")

And so as always I do:

git add test.py
git commit -m "updating test.py"
git push -u origin master

which gives:

Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 8 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 281 bytes | 281.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (2/2), completed with 2 local objects.
remote: Internal Server Error
Everything up-to-date

However, the changes are not seen on the github page. Now, git status gives:

On branch master
Your branch is ahead of 'origin/master' by 1 commit.
  (use "git push" to publish your local commits)

nothing to commit, working tree clean

Could anyone please help?

1

The (internal server error) message is typically representative of a Github outage. The status of GitHub can be observed at

The issue continued for 2 days and then without changing anything, the 'git push' went through.

James H. Sterling

James H. Sterling

Environmental Science & Climate Journalist

James Sterling reports on renewable energy developments, climate policy, ecological conservation, and green tech innovations around the globe.

Share this article
Twitter Facebook Pinterest