Commits are not appearing in my contribution graph

[Its-Seeker]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Code Search and Navigation

Body

Hello,

My commits are not appearing in my GitHub contribution graph or activity feed.

Details:

• GitHub username: Its-Seeker
• Repository is public
• Repository is not a fork
• Commits are on the default branch (main)
• Email is verified and matches commit author email
• Commits are visible in repository history
• Contribution activity only shows "Created 1 repository"

I have verified my Git configuration, email, branch, and repository settings.

Could someone help identify why my commits are not being counted as contributions?

Thank you.

[fs-shariyar-bd]

Possible reasons your commits aren't showing up:
GitHub only counts a commit toward your contribution graph if all of the following are true:

1.Email match – The email used in the commit must be added and verified under your GitHub account (Settings → Emails). You can check which email was used with : git log --format='%ae' -n 5
If it doesn't match any of your verified emails, that's likely the issue.

2.Branch – The commit must be on the repository's default branch (or gh-pages). Commits sitting on a feature/topic branch that hasn't been merged yet won't count.

3.Repository visibility – If the repo is private, make sure "Include private contributions on my profile" is enabled in your profile settings. For public repos, this isn't needed.

Suggested fix: Check if your commit email matches a verified email on your GitHub account first, since that's the most common cause—especially when working on a copied or transferred repository.

More details here: https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile

[daniyal-debug]

Hello everyone,

I'm experiencing an issue where my commits are not showing up in my GitHub contribution graph or contribution activity, even though the commits are visible in my repository.

What I've Verified
My repository is public.
The repository is not a fork.
Commits were made to the default branch (main).
The commit email matches a verified email address on my GitHub account.
The commits are visible in the repository's commit history.
GitHub is only showing "Created 1 repository" in my contribution activity.
Additional Information
GitHub username: Its-Seeker
Repository: node
I have already checked my Git configuration, verified email settings, and repository settings.
My Question

Could someone help me identify why these commits are not being counted as contributions? If there are any additional checks or common issues that I might have missed, I would greatly appreciate your guidance.

Thank you for your time and assistance.

[fs-shariyar-bd]

Since you've already ruled out the common causes (visibility, fork status, branch, email match), there are a couple of less-obvious things worth checking:

Caching/sync delay. GitHub's contribution graph doesn't always update instantly — it can take a few hours, and occasionally needs a manual rebuild on GitHub's end. If your commits are very recent, this might just resolve itself.
One contribution must already be required for the repo to "count" you. GitHub requires that you be a collaborator on the repo, or that you've starred/forked/opened a PR or issue in it — just owning it and pushing commits should normally satisfy this, but it's worth double-checking the repo isn't set up in an unusual way (e.g. created via "Use this template" rather than a normal git init/git push, since template-generated initial commits can sometimes behave differently).
Check the actual commit author info via the API, not just local git config — sometimes GitHub Desktop or another tool used a different identity than what git config shows locally. You can check this by adding .patch to the end of a specific commit URL (e.g. github.com/user/repo/commit/HASH.patch) and looking at the From: email in the raw output.
If none of this resolves it, this might genuinely need GitHub Support — at that point it's likely an account-specific indexing issue rather than something fixable from the user side.