Repository commits not appearing on contribution graph

[Manula413]

Select Topic Area

Question

Body

I’m running into an issue where some commits aren’t showing up on my GitHub contribution graph, even though they exist in the repository history.

What’s happening:

• I made multiple commits (5 total) within a short time window using GitHub’s web editor
• All commits are visible in the repository’s commit history
• Only one of those commits appears on the contribution graph

Context / things I’ve checked:

• The repository is private
• “Include private contributions” is enabled in profile settings
• Commits were made directly via GitHub (not local Git), so email config shouldn’t be an issue
• All commits were made to the default branch
• I waited over 24 hours for the contribution graph to update
• This isn’t a one-off, I’ve noticed this behavior multiple times in the past

Question:
Why would GitHub count only some commits toward the contribution graph when all commits are on the same branch, visible in the repository’s commit history, and made via the GitHub web editor?

Are there any documented rules or known behaviors (such as commit aggregation, timing, or internal filtering) that cause certain commits to not register as contributions, even though they exist in the repo?

Thanks in advance

[DilshanNarankotuwa]

GitHub doesn’t count “all commits that exist anywhere in the repo history” toward the contribution graph it only counts commits that meet very specific rules, and the most common reason you’ll see some commits count while others don’t (even if they were all made via the web UI) is that only certain commits actually end up on the default branch with you as the recognized author. For commits to show on the graph they must be authored with an email that’s associated with your GitHub account (including your GitHub-provided noreply address), be in a standalone repo (not a fork), and be on the repo’s default branch or gh-pages; plus you must be a collaborator/member (or have forked/opened a PR/issue there). In practice, this “only one of five shows up” pattern often happens when the web editor silently routes changes through a PR because the default branch is protected, and the PR is merged with Squash (or sometimes rebase), meaning only one commit lands on the default branch while the other commits remain only on the PR branch (they still “exist” and are visible in the repo/PR history, but they don’t qualify for the contribution graph because they aren’t on the default branch). Another common cause is that some of the commits have an author email that GitHub can’t link to your account (you can confirm by opening the commit and appending .patch to the URL and checking the From: line), in which case those commits won’t count until that email is connected/verified (and note: managed/enterprise accounts can have stricter limits on what emails can be associated). If you want to diagnose it quickly, pick one “missing” commit and (1) check whether it’s reachable from the default branch (the commit page usually shows which branches contain it), and (2) check the author email via .patch; if either fails, GitHub is behaving “as documented,” and the fix is usually “merge the changes so the commit exists on the default branch” or “make sure the commit’s author email matches a verified email on the account.”