Git push fails with repository not found error on GitHub

Other Questions Github
1

I keep getting an error when I try to push my code changes to my GitHub repo using git commands. The error message says:

> git push origin main
remote: Repository not found.
fatal: repository 'https://github.com/CompanyName/ProjectName.git' not found

The weird thing is that I know the repo exists and I have the right permissions. I can edit files directly on the GitHub website and pull those changes to my computer just fine. I’m using Windows Git Credential Manager to handle my login stuff. My git config looks like this:

[credential]
    helper = manager

I’m on Windows 10 with git version 2.10.2. Has anyone else run into this issue before?

2

Check if your remote URL points to the right repo. When repos get renamed or moved, your local git config doesn’t update automatically. Run git remote -v to see what URL you’re pushing to. I had this exact problem last month when our company changed their GitHub org name. The repo existed but my local clone was still trying to push to the old URL. You can fix it with git remote set-url origin <new-url>. Also check if you have branch permissions. Some repos block pushes to main and require pull requests instead. Try pushing to a different branch first to see if it’s a branch protection thing.

3

That ‘repository not found’ error usually means your Git credentials are cached but expired or wrong. Your local Git client’s probably using old auth tokens even though the web interface works fine.

I’ve hit this same issue tons of times. Quickest fix is clearing your credential cache:

git credential-manager-core erase

Then try pushing again - Windows will ask you to re-authenticate.

Honestly though, Git auth headaches are exactly why I automated all my deployment workflows. No more fighting with credentials or manual pushes - just set up automated pipelines that handle everything.

Latenode makes this dead simple. You can create workflows that auto-push code changes, run tests, and deploy to different environments without touching Git commands. It connects directly to GitHub and handles all the auth behind the scenes.

I use it for everything now since it completely eliminates these credential issues. Workflow triggers on code changes and handles the entire pipeline automatically.

4

your credential manager’s probably holding onto old github tokens. go to control panel > credential manager and manually delete any github entries, then try pushing again. also, git 2.10.2 is ancient - upgrading to a newer version will fix a lot of auth issues.