iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A commit can be visible in a repository and still be missing from your GitHub contribution graph. GitHub counts only activity that meets its attribution, repository, branch, and account-relationship rules; private activity is also hidden by default. Check those conditions in order before changing anything. GitHub’s profile contribution rules are the basis for the checks below.
First, know what the graph does—and doesn’t—count
Your contribution graph is not a complete record of open-source work. It displays qualifying GitHub activity, not every commit or task you performed. For a commit to count, GitHub requires an account-associated author email, an eligible repository and branch, and at least one qualifying relationship to the repository.
Issues, pull requests, and discussions have their own criteria: they must be opened in a standalone repository, not a fork, and GitHub limits how many of these items appear on the graph. Opening a repository and forking an existing repository are also listed as profile contributions, but commit and issue-related activity are conditional.
Check the commit’s author email
GitHub attributes a commit to an account using the email recorded in the commit—not simply the username configured on your computer. The recorded address must be associated with your GitHub account. On GitHub.com, this can be an address added to your account or the GitHub-provided noreply address shown in your email settings.
- Open the commit on GitHub and view its
.patchversion. For example, add.patchto the commit URL. - Find the
From:line and check the email address shown there. - If it is an old address you control, add that exact address to your GitHub account’s email settings. GitHub says it will rebuild attribution for commits using the address; allow up to 24 hours for the graph to refresh.
An address such as jane@computer.local cannot be linked to a GitHub account. If the From: address is wrong, correct the email used for future commits; adding a historical address only helps when it is the address actually recorded on those commits. See GitHub’s missing-contributions troubleshooting guide.
Confirm the commit is on an eligible branch
GitHub counts commits on a repository’s default branch or, for a project site, its gh-pages branch. Work on a feature branch may be visible in the repository without counting yet. If it fits the project’s normal workflow, open a pull request and have it merged into an eligible branch.
Changing a repository’s default branch is another documented possibility, but it is an administrative decision that can affect collaborators and project workflows—not a routine personal setting to change just to alter a graph. The contribution reference and the troubleshooting guide describe the branch requirement.
Check whether the repository is a fork
Commits made in a fork do not count on their own. GitHub says they can count if you open a pull request and the changes are merged into the parent repository. Issues, pull requests, and discussions opened in a fork likewise do not meet the standalone-repository requirement.
If your work is in a fork, check whether a pull request to the parent repository is appropriate for the project. The graph rule does not mean you should submit changes the maintainers have not asked for or bypass the project’s contribution process.
Check your relationship to the repository
Even with the right email, repository, and branch, a commit must meet at least one of GitHub’s relationship conditions. You must be a collaborator or organization member, have forked the repository, or have opened an issue or pull request in it. If none applies, the commit may not qualify for the graph. See GitHub’s full eligibility reference.
Make sure activity is not just hidden
Private and internal contributions are hidden from your graph by default. If you want them represented, open your profile’s contribution settings and enable the option to show private contributions. People who cannot access those repositories see anonymized daily counts, not repository names or private details. The setting changes visibility; it does not make an ineligible commit qualify.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Organization SAML single sign-on can also affect whether you see organization activity when you do not have an active SSO session. Check that session if the missing activity is associated with an organization. GitHub explains graph visibility in Contributions on your profile and links to the relevant controls in Managing contribution settings on your profile.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check the date, then allow time for the graph to update
GitHub places commits on the profile graph using the Git author date; repository views use the commit date. Rebasing, amending, or force-pushing can make those dates differ. Graph dates use UTC, so a commit made near midnight may appear on a neighboring day compared with your local time.
After a commit meets the requirements, GitHub says it may take up to 24 hours to appear. If it is still missing after that, recheck the From: address in the commit’s .patch view and confirm the branch, repository type, relationship, and visibility conditions. If those checks are satisfied, contact GitHub Support through the troubleshooting guidance.
Keep the graph’s scope in perspective
The profile graph shows activity over the past year; it is not a lifetime ledger or a measure of the quality or amount of someone’s open-source labor. A missing square means the activity is not being displayed as a qualifying contribution under GitHub’s rules—it does not prove the work was not done. GitHub Enterprise Server also has a separate contribution-sharing reference for the past 90 days; that scope should not be confused with the GitHub.com profile graph. See the contribution reference.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
