pushing with wrong github account from visual studio 2026

[MBPpp]

🏷️ Discussion Type

Question

Body

i have 2 github accounts, and whenever i push in visual studio 2026, it brings up a pop-up for me to choose an account. i choose the one i want, and then it pushes. i go to github, or look in the code in vs, or whatever, and it never actually says the account i picked. it always says i pushed with the other account.

all answers i've found on the internet tell me to, in some way, remove the other account entirely from my computer, but i do actually need both. one of them is this account, and the other is a school account for school projects and stuff. i wanna keep that stuff separated, so i don't want to just remove this account.
i even did go ahead and removed this account (which is the wrong one i've been talking about) from visual studio entirely, and it still does the select account pop-up, and it still pushes with this account instead of my school account.

how do i fix this?

[sgdev-official]

Hey! I totally get how frustrating that is. You want to post or push your school stuff under your school account, but Visual Studio stubbornly keeps routing it to your personal one, no matter how many times you pick the right account in that pop-up window.

The reason this happens is that Visual Studio's account switcher is just a UI layer—behind the scenes, Git is looking at Windows Credential Manager and your local repository settings, which are silently overriding whatever you select.

Here is the most reliable way to fix it without having to delete either of your accounts:

1. Clear out the cached GitHub credentials in Windows

   • Open the Windows Start menu, type Credential Manager, and open it.
   • Click on Windows Credentials.
   • Look for any entries that mention git:https://github.com or GitHub tokens, click them, and hit Remove. (This forces your computer to stop auto-logging in with the wrong account).

2. Lock down the correct account inside your school repository folder

   • Open your school project folder in a terminal (or Git Bash).
   • Run these commands to bind that specific folder permanently to your school account details:

     git config user.name "Your School GitHub Username"
     git config user.email "your-school-email@example.com"

   • Verification: Run git config user.name inside that folder to make sure it displays your school username.

Once you do that, Git will stop guessing and will always use the correct account for that specific project, while leaving your personal projects untouched!

[MBPpp]

this worked, thank you so much :]

[nikoladimitrov98]

The legacy-peer-deps explanation above is the most common cause. A few other things are worth checking, because the setting can come from places that npm config get makes easy to miss.

1. Make sure local and CI use the same npm version

npm -v

npm 6 ignored peer dependency conflicts, and npm 7 and later treat them as errors. If you run a newer npm locally than your CI image does (or the other way round), the same lockfile can pass in one place and fail in the other. Make CI match your local version, either by setting the same Node version in your CI setup step or by adding npm install -g npm@<your-version> before npm ci.

2. Find where the setting comes from

npm config ls -l | grep -i peer

It can be set in your user ~/.npmrc, in a global npmrc, or as an environment variable (NPM_CONFIG_LEGACY_PEER_DEPS). None of those get committed, so CI never sees them. If you really need the setting, put it in a project-level .npmrc and commit it, so local and CI behave the same. Fixing the conflict is still the better fix.

3. Reproduce the CI failure locally

npm ci

npm ci deletes node_modules and installs strictly from the lockfile, which is exactly what CI does. Running npm install in a folder that already has a node_modules doesn't test the same thing, so it can pass even when CI fails.

4. Read the ERESOLVE message

The error has three parts that name the conflict:

• While resolving: is the package doing the install.
• Found: is the version you actually have.
• Could not resolve dependency: peer ... is the version range that package expects.

Then ask why each version is in your tree:

npm explain <package-name>
npm ls <package-name>

5. Fix it at the source

• Usually you can upgrade the package that declares the peer to a release that supports your version, or move your version into its range.
• If the peer range is just out of date and the package works fine, you can try overrides in package.json. It's written down and reviewable, unlike --force. Peer dependency conflicts can still fail with overrides in place, though (npm/cli#8470), so upgrading the package is the more reliable fix.
• Then regenerate and test:

rm -rf node_modules package-lock.json
npm install
npm ci

Commit the new lockfile once npm ci passes.

[MrFabry]

The account you pick in that popup is only what Git logs in with for the push. The name GitHub shows on a commit comes from the email stored inside the commit, and that comes from your Git config, not from the account you push with. So you're most likely authenticating as the school account and pushing commits stamped with your personal email, and GitHub links them to the personal account.

You can check it inside the school repo:

git log -1 --format="%an <%ae>"

If that shows your personal email, that's the whole problem, and you don't need to remove anything from Credential Manager or Visual Studio.

Set it per repo so your own projects stay as they are. In Visual Studio go to Git > Settings, expand Git Repository Config (Git Repository Settings in 2022) and put the school name and email there. Or from a terminal in the school repo:

git config user.name "your-school-username"
git config user.email "school-email@example.com"

No --global, so it only applies to that repo. The email has to be added and verified on the school account (or use that account's noreply address from Settings > Emails), otherwise GitHub won't link it to anyone.

If all your school stuff is under one folder you can make it automatic. Add this to your global config (C:\Users<you>.gitconfig):

[includeIf "gitdir/i:C:/School/"]
    path = .gitconfig-school

and create .gitconfig-school next to it with a [user] section for the school account. Every repo under C:/School/ picks it up.

Commits you already pushed keep the old email. To fix the last one:

git commit --amend --reset-author --no-edit
git push --force-with-lease

For several, git rebase -r <commit-before-the-first-wrong-one> --exec "git commit --amend --no-edit --reset-author" and then the same push. It rewrites history though, so only on branches nobody else is working on.