-
Select Topic AreaQuestion BodyHey, I'm currently connected with user A : I'm trying to push on a repo of user A but there is an error : I added user B on user A's repoand it worked. And it was user A who commited on the repo not user B. What can I do please ? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
This comment was marked as off-topic.
This comment was marked as off-topic.
-
With the command it didn't work (fatal: credential-cache unavailable; no unix socket support), but it succeed with removing it manually on windows credential manager. Thank you ! |
Beta Was this translation helpful? Give feedback.
-
Hey there! 👋 Thanks for posting in the GitHub Community, @Smachy24! We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category. The Accessibility category is a place for our community to discuss and provide feedback on the digital accessibility of GitHub products. Digital accessibility means that GitHub tools, and technologies, are designed and developed so that people with disabilities can use them. I've gone ahead and moved this to the correct category for you. Good luck! |
Beta Was this translation helpful? Give feedback.
Remember, changing user.email and user.name in Git config only affects commit authorship, not GitHub authentication.
1. Cache Credentials: Sometimes the issue can be with cached credentials on your machine. You can clear these out and re-enter them when prompted. On most systems, you can use the git credential-cache exit command to clear the cache.
2. Try Fresh Clone: If issues persist, clone the repository again with user A's credentials.