Trace your commute

Public coding profiles and commit identity

What GitHub profiles and commit email can reveal

Profile fields, public activity, daily contribution counts and commit email have separate visibility controls. A private profile does not erase public repository activity.

Sources checked .

Conceptual illustration

A profile brings several kinds of information together

GitHub lists profile text, a picture, pinned repositories or gists, contribution activity, status and achievements as profile elements. Details added to a public profile are visible to other GitHub users. GitHub: profile elements and private-profile exceptions

Private profiles still have public exceptions

GitHub says a private profile hides its contribution graph, activity feed, memberships and several other elements. A README, bio and profile picture can remain public. The setting does not offer a selected-viewer exception. GitHub: profile elements and private-profile exceptions

Repository activity has a separate audience

GitHub says making a profile private does not remove or hide past activity. Activity in public repositories remains visible to people viewing those repositories, and some activity data can remain available through the API. Profile privacy should not be treated as repository access control. GitHub: public repository activity and private-profile limits

Commit email is separate from a profile preference

GitHub uses the commit email to associate a commit with an account. Browser-based operations and command-line Git use separate configuration routes. Earlier commits remain associated with the email used before a change. GitHub: commit attribution and earlier email records

A noreply address can still identify the account

GitHub documents noreply formats containing a username, or an account ID plus username, depending on account age and settings. That format protects a personal mailbox address without promising an unlinked identity. The reference also distinguishes username-change behavior for older and ID-based addresses. GitHub: noreply address formats and account linkage

The email push guard has a documented scope

GitHub says its optional email push protection checks the most recent commit. It blocks when that commit's author email is a private email on the account. This is a defined check, not a stated scan of every historical email in every commit. GitHub: most-recent-commit email check

Private contribution counts can still reveal a daily pattern

GitHub says publicizing private contributions lets viewers without repository access see the number contributed each day, without specific details. Daily counts and access to the underlying work are different disclosures. GitHub: daily private contribution counts

Questions and answers

Does a private GitHub profile make public repository activity private?

GitHub says activity remains visible in the public repositories themselves. GitHub: public repository activity and private-profile limits

Will changing my commit email replace it in old commits?

GitHub says earlier commits remain associated with their previous email. GitHub: commit attribution and earlier email records

Can people see daily counts from private repositories?

If private contributions are publicized, GitHub says daily counts are visible without specific details. GitHub: daily private contribution counts

Sources and scope

Public GitHub.com documentation checked 10-24-2026. These are documented profile, contribution and commit-email behaviors, not an inspection of a private account, repository or Git configuration. Some enterprise-managed accounts and organization rules differ.

Keep exploring