Unable to git push to my own repo

[AthArvA-188]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Misc

Discussion Details

I am not able to push to my own repo after committing changes.
reason:
fatal: Authentication failed for 'my repo's address'

I tried doing the 'git remote -v' and it is showing the correct repo

after that I tried running the commands for PAT token and still got some errors:
git: 'credential-manager-core' is not a git command. See 'git --help'.
git: 'credential-manager-core' is not a git command. See 'git --help'.
remote: Invalid username or token. Password authentication is not supported for Git operations.

[VictorMoni]

The error happens because GitHub removed password authentication for Git pushes. You need to use a Personal Access Token (PAT) instead of your GitHub password. Here are the steps:

1. Generate a new PAT in your GitHub settings → Developer settings → Personal Access Tokens.

   • Make sure to select scopes like repo (for private repos).

2. Update your remote to use HTTPS with the token:

git remote set-url origin https://<USERNAME>@github.com/<USERNAME>/<REPO>.git

I hope it helps 🙏

[AthArvA-188]

I am running this on Windows PowerShell
And after running the command in '3', I am not getting anything to paste the password in (or do I just have to add the PAT on the next line ?)
Where will I have to put my PAT after running 3?
Guide me

[VictorMoni]

When you run step 3 (git remote set-url ...), Git doesn’t ask for the PAT yet.
The token is only requested the first time you do a git push or git pull.

So the flow is:

1. Run git push origin main (or your branch).
2. Git will ask for your username → enter your GitHub username.
3. Git will ask for your password → paste your Personal Access Token (PAT) instead of your old password.

Tip: If you don’t want to enter the PAT every time, you can cache it:

git config --global credential.helper store

[AthArvA-188]

(base) PS D:\vsg\studio> git remote set-url origin https://AthArvA-188@github.com/AthArvA-188/studio.git (base) PS D:\vsg\studio> git push origin master Enumerating objects: 17, done. Counting objects: 100% (17/17), done. Delta compression using up to 24 threads Compressing objects: 100% (7/7), done. Writing objects: 100% (9/9), 3.27 KiB | 3.27 MiB/s, done. Total 9 (delta 5), reused 0 (delta 0), pack-reused 0 (from 0) remote: Resolving deltas: 100% (5/5), completed with 5 local objects. To https://github.com/AthArvA-188/studio.git 4c2333b..0bd6fed master -> master

It didn't asked any username or password
Is it done or not?

[AthArvA-188]

Thank you very much, you were a great help!!

[VictorMoni]

You're welcome @AthArvA-188 😁👍

I'm sorry I couldn't solve 100% of the problem, but if there's anything else I can do for you, please just ask — I'll be glad to help you.

Happy coding 🚀

[devstar222696]

HI, @AthArvA-188
Your errors show you’re pushing over HTTPS with a password (not allowed) and your credential helper isn’t set up.

Root cause

• GitHub blocks passwords for Git over HTTPS → you must use a PAT or SSH.
• credential-manager-core not found → credential helper missing/misconfigured.

Fix (pick one)

A) HTTPS with a Personal Access Token (PAT)

1. Create a PAT

• Fine-grained: repo access with Contents: Read and write (and authorize SSO if used), or

• Classic: scope repo.

2. Configure credential storage

• Windows: git config --global credential.helper manager (install Git Credential Manager if needed)

• macOS: git config --global credential.helper osxkeychain

• Linux: git config --global credential.helper store (or libsecret if available)

3. Push and, when prompted:

• Username: your GitHub username

• Password: the PAT (paste the token)

Fast path:

gh auth login   # HTTPS → "Login with a web browser"
gh auth setup-git
git push

B) SSH (no tokens)

ssh-keygen -t ed25519 -C "you@example.com"
eval "$(ssh-agent -s)"; ssh-add ~/.ssh/id_ed25519
# Add ~/.ssh/id_ed25519.pub to GitHub → Settings → SSH and GPG keys
ssh -T git@github.com
git remote set-url origin git@github.com:OWNER/REPO.git
git push

If it still fails

• Clear cached bad creds:
  - Windows Credential Manager / macOS Keychain / Linux keyring → remove github.com entries.
• Recheck scopes/SSO authorization on the PAT.
• Verify remote: git remote -v shows either https://github.com/... or git@github.com:....

[devstar222696]

Nice 👍 since git config --global credential.helper manager ran successfully, Git is now set to use Git Credential Manager (GCM).

1. Make sure your remote is HTTPS
   Check:

git remote -v

It should look like:

https://github.com/<username>/<repo>.git

If it still shows git@github.com:..., that’s SSH, and PATs won’t work. Fix it with:

git remote set-url origin https://github.com/<username>/<repo>.git

2. Generate a PAT (if not already done)

• On GitHub: Settings → Developer settings → Personal access tokens

• Choose either:

  • Fine-grained token → add repo access with Contents: Read and write, and authorize for your org if SSO is required.

  • Classic token → scope repo.

• Copy the token (it’s shown only once).

3. Push to trigger login

Now run:

git push origin <your-branch>

• Username: your GitHub username (not email; but any string technically works).
• Password: paste your PAT.

GCM will then store the token securely in Windows Credential Manager. Next pushes won’t ask again.

4. Verify it’s saved
   Check:

git credential-manager get

(or open Windows Credential Manager → Windows Credentials → look for git:https://github.com).

After this, pushes should just work without prompting again.

[AthArvA-188]

git remote set-url origin https://github.com//.git (done)
git push origin (done)

After running this it didn't asked for any of Username or the password it gave this:

Enumerating objects: 17, done.
Counting objects: 100% (17/17), done.
Enumerating objects: 17, done.
Counting objects: 100% (17/17), done.
Delta compression using up to 24 threads
Delta compression using up to 24 threads
Compressing objects: 100% (7/7), done.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (9/9), 3.27 KiB | 3.27 MiB/s, done.
Total 9 (delta 5), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (5/5), completed with 5 local objects.
To https://github.com/AthArvA-188/studio.git
4c2333b..0bd6fed master -> master

[devstar222696]

Perfect 🎉 That output means your push succeeded — your commits are now on GitHub.

[devstar222696]

The reason you weren’t asked for username/PAT is that Git Credential Manager (GCM) stepped in, found valid credentials (either cached from earlier or picked up automatically from GitHub CLI/Windows Credential Manager), and used them silently.
That’s exactly what it’s supposed to do.

[AthArvA-188]

Thank you very much, Legend!

[devstar222696]

You are welcome!

[metinmeki]

Hey, GitHub stopped using passwords for Git. You need a Personal Access Token (PAT) to push.

Generate a PAT on GitHub with repo access.

Update your remote:

git remote set-url origin https://:@github.com//.git

Push again.

Or use SSH to avoid the token