What the setting actually does
Your GitHub contribution graph can look quiet even when you are shipping constantly.
That happens because, by default, GitHub only counts work in public repositories.
If most of your commits land in private repos, visitors see a sparse calendar that understates how active you really are.
GitHub lets you change this.
You can turn on private contribution visibility so your graph includes private repo activity, with the details anonymized.
This article explains what that setting actually reveals, what it hides, and how to decide whether it fits your situation.
According to GitHub's documentation, your contribution graph and Achievements show only public repository activity by default.
You can choose to include private repositories too, and when you do, the specific details of that private activity are anonymized (GitHub Docs).
Anonymized means viewers see that something happened, not what happened.
A square on the calendar may fill in, but visitors cannot see the private repo name, the commit messages, or who you worked with.
People outside an organization also see anonymized contribution activity for that organization's work (GitHub Docs).
So the tradeoff is narrower than many people assume.
You are not exposing your code or your client's roadmap.
You are exposing the fact that you were active, and roughly how much.
What viewers can and cannot see
Even with private contributions enabled, the details stay hidden.
But there are related settings and behaviors worth understanding before you flip the switch.
- The graph itself. With the setting on, private activity fills the calendar. With it off, only public work appears.
- The activity overview. If you enable the activity overview section, viewers can see more about the types of contributions you make and the repositories you are most active in. However, a viewer only sees information about repositories they already have read access to (GitHub Docs). Private repos stay invisible to strangers there too.