Review GitHub profile and commit-email privacy

Review the fields that remain public

GitHub says a README, bio and profile picture can remain publicly visible on a private profile. Review those fields separately before assuming the profile switch hides them. GitHub: profile elements and private-profile exceptions

Locate the profile privacy choice

GitHub documents Settings > Public profile > Contributions & Activity, then Make profile private and hide activity and Update preferences. Read the current choice and its effects before deciding whether to change it. GitHub: private-profile control

The reference says private profiles cannot receive GitHub Sponsors sponsorships. Public repository activity and some API data can remain visible, so weigh the profile option against how the account is used. GitHub: public repository activity and private-profile limits

Review browser-based commit email

GitHub documents Settings > Emails and the email privacy checkbox for browser-based Git operations. With privacy enabled, the author email for those operations defaults to noreply. This does not configure command-line Git on every computer. GitHub: browser and repository-local email controls

Review the email in each relevant local repository

GitHub documents repository-local email configuration separately from the global setting. The local choice overrides the global choice for that repository. Its guide shows git config user.email to confirm the value and permits the GitHub-provided noreply address. Check the repository and client used for future commits. GitHub: browser and repository-local email controls

Use the account-provided noreply value

The noreply format depends on account age and privacy settings. Use the value provided for the account instead of inventing an address. A username-based address and an ID-based address have different username-change behavior. GitHub: noreply address formats and account linkage

Read the push-blocking option with its limits

GitHub documents the email privacy and email-exposing push-block checkboxes under Settings > Emails. The documented check examines the most recent commit's author email against private emails on the account. Review local configuration too; this option is not described as an audit of all old commits. GitHub: most-recent-commit email check

Review contribution counts and achievements separately

GitHub documents Your profile > Contribution settings > Private contributions to show or hide private-contribution activity. It separately documents an achievements preference in Settings and a way to hide an individual achievement. These are separate choices. GitHub: private contribution and achievement controls

Keep earlier records separate from future preferences

GitHub says old commits stay associated with their previous email address after a configuration change. Review future configuration without assuming it rewrites published history. This guide does not recommend changing shared repository history as a routine privacy toggle. GitHub: commit attribution and earlier email records