Random account appears as contributor on private repo

[Squirrelcoding]

Select Topic Area

Bug

Body

I was just creating a small Discord bot with nothing more than a couple python files. I'm very sure that I configured by account correctly on git, but when I made the commit and looked at it on the website, it says that a user called "WHYNoT3667" (who simply joined June 13 and has no other contributions) did the commit. I have no relation to whoever this is. What's going on? Is this some sort of bug? And when I look at the commits and click on their username on the top right, it doesn't list them, but rather only my name.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Squirrelcoding]

?

[VishalKotekar]

The issue seems to be that a random account appears as a contributor on your private GitHub repo. This could happen if commits were made with misconfigured Git settings or if another user’s identity was mistakenly linked to the commits.

To resolve this:

1. Verify your Git user configuration with git config --global user.name and git config --global user.email.
2. Check if your commits were signed with the correct credentials.
3. You can amend the commit history if necessary.

Let me know if you need further clarification!

[zshaian]

This happened to me as well, and I realized that I was the one who made the commit. However, it showed a different user in the commit history. After double checking my git config, I found that my gitHub email didn’t match the one I was using for the commits. This mismatch is likely why a different user appeared. I suggest you double check your git configuration using git config --global user.email just to make sure it matches your github email.

[mikk1max]

Try to follow all of these steps, maybe some of them will help you

1. GitHub identifies users by email address in the commit metadata.

git log --pretty=format:'%h %an %ae'

2. Check for any unauthorized SSH keys or access tokens. If someone else has your credentials or an access token, they might be able to push commits on your behalf. Review your GitHub account's SSH and GPG keys, as well as any Personal Access Tokens or OAuth Apps under Settings.

3. Given that this happened on a private repository and the username doesn't appear in certain areas, it's possible there's a minor bug or glitch in how GitHub is displaying the commits. You could try:

   • Re-cloning the repository and examining the commit history.
   • Contacting GitHub support if the issue persists after checking your configuration.

If none of these solve the issue, it might be worth reviewing the project's access settings and running a security check to ensure no one else has unauthorized access to the repo.