remote: fatal error in commit_refs

[ChaeMendoza]

Select Topic Area

Question
git push
Error

Body

I'm facing difficulties when trying to push changes to the branch in my repository. Whenever I attempt to push, I receive the following error message:

Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
remote: fatal error in commit_refs        
To https://github.com/my_path_project.git
 ! [remote rejected] new-tests -> new-tests (failure)
error: failed to push some refs to 'https://github.com/my_path_project.git'

I've tried several solutions, such as checking permissions, resolving conflicts, and verifying the remote URL, but I haven't been able to resolve the issue yet.

Could anyone provide guidance or suggestions on how to fix this problem?

[Milton-dynasoft]

i have the same issue! Help

[gurjeetsinghvirdee]

Hey @ChaeMendoza
can you share your repo & in which branch you are trying to push

[gurjeetsinghvirdee]

is your branch protected?

[gurjeetsinghvirdee]

Can you check in any of your other repositories or company repositories to see if they have the same problem? If it's the same, then it's likely a GitHub issue. Otherwise, there may be some issues on your company's side. Perhaps they made changes to protect the branch or implemented other security measures related to their repository.

[gurjeetsinghvirdee]

https://errorforge.com/resolving-the-remote-fatal-error-in-commit_refs-in-git/

[ChaeMendoza]

Hi @gurjeetsinghvirdee
I just wanted to inform you that the issue I was experiencing with pushing to my repository has been resolved automatically. It seems that the incident on April 24, 2024, related to GitHub, might have been the cause of the problem.
https://www.githubstatus.com/history

[ReinaldoVillegas]

I have the same problem pls helppp!!!

[gurjeetsinghvirdee]

you have too company repo? or it's a issue in your repository

[ChaeMendoza]

@ReinaldoVillegas

I wanted to let you know that the issue you mentioned, which I also experienced, seems to have been resolved. It appears that it was related to the incident on April 24, 2024, on GitHub.

Could you please try pushing again to see if the problem has been resolved for you as well?