Contribution graph not updating for verified-and-API-attributed commits (1+ week)

[numesh4]

I have commits that GitHub's own API confirms are correctly attributed to my
account, but they still aren't showing on my contribution graph after more
than a week. A support ticket I raised was closed and pointed to self-service
docs, but those docs assume the email isn't verified yet, mine already is,
and the API confirms attribution, so I don't think that's the issue here.

Repo: numesh4/multi-touch-attribution-dbt (public, not a fork)
Example commit: 850e4af1e895d8ab6b3868c904994c4c59bc36a1
Commit author email: (verified on my account, confirmed
under Settings > Emails)
Branch: main (the repo's default branch)

Checking the commit via the API:

GET /repos/numesh4/multi-touch-attribution-dbt/commits/850e4af

returns a top-level "author" object correctly linked to my account:

"author": { "login": "numesh4", "id": 22649315 }

So GitHub has already matched the commit email to my verified account this
isn't an unverified-email situation. Several other commits from the same
period (Aug 17-18) show the same correct attribution. Despite that, none of
them appear on my contribution graph, over a week later.

This looks like the same issue reported in #198780, where a re-indexing step
apparently didn't complete even though support said they could trigger it
manually and a second commenter on that thread reported the identical
symptom, suggesting it's not isolated.

Could someone from GitHub staff take a look at re-indexing my account's
contribution graph, or point me to what else could cause a correctly
API-attributed commit to be excluded from the graph? Happy to provide any
further commit SHAs or account details needed.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[tahleho3968]

Helpful distinction: the API reporting "author": { "login": "numesh4" } means GitHub has linked the commit's email to your account — but the contributions graph is stricter than attribution alone. All of the following must hold:

1. Author email, verified, exact. It's the author email that counts, and it must match a verified address byte-for-byte. Append .patch to https://github.com/numesh4/multi-touch-attribution-dbt/commit/850e4af...patch and compare the From: address to your Settings > Emails list — exact match, including case/domain. A near-identical variant will still "link" via API fuzzy matching yet fail the graph's exact check.
2. On the default branch. Confirm GET /repos/numesh4/multi-touch-attribution-dbt → default_branch is actually main (a branch named main isn't automatically the default). Commits anywhere else don't count until they land on the default branch via a merge/PR.
3. Not in a fork. Yours is a standalone public repo, so this is satisfied.
4. Within the rolling year and past the refresh window. Qualifying commits should appear within ~24 hours of the email being linked.

Your commit looks like it should qualify, so the most probable causes are (a) the exact author-email check, or (b) a graph/index refresh lag of the kind #198780 documents. Practical next steps:

• Verify the From: author email on 850e4af via .patch and confirm it's an exact match.
• If it's exact and still missing after 24h, open a GitHub Support ticket referencing Contribution graph not updating after re-adding verified email #198780 with the commit SHA — that thread records support forcing a manual graph re-index for this same symptom.

[numesh4]

Hi Tahleho, Thanks for your response. I've checked the following - 850e4af's author/committer email ***@***.***) matches git config and 24 of 26 commits. Two other commits use another email, which is a verified email address as well (under my emails settings). So should count towards the contributions as well. Both emails are verified with the original email being the default. - Also confirming the default branch is actually *main; *no other branch exists on the repo. Anything else I can try? Thanks Nikash

…

On Sun, Aug 30, 2026 at 9:12 AM Tahleho Paki ***@***.***> wrote: Helpful distinction: the API reporting "author": { "login": "numesh4" } means GitHub has *linked* the commit's email to your account — but the contributions graph is stricter than attribution alone. All of the following must hold: 1. *Author email, verified, exact.* It's the *author* email that counts, and it must match a verified address byte-for-byte. Append .patch to https://github.com/numesh4/multi-touch-attribution-dbt/commit/850e4af...patch and compare the From: address to your Settings > Emails list — exact match, including case/domain. A near-identical variant will still "link" via API fuzzy matching yet fail the graph's exact check. 2. *On the default branch.* Confirm GET /repos/numesh4/multi-touch-attribution-dbt → default_branch is actually main (a branch named main isn't automatically the default). Commits anywhere else don't count until they land on the default branch via a merge/PR. 3. *Not in a fork.* Yours is a standalone public repo, so this is satisfied. 4. *Within the rolling year and past the refresh window.* Qualifying commits should appear within ~24 hours of the email being linked. Your commit looks like it *should* qualify, so the most probable causes are (a) the exact author-email check, or (b) a graph/index refresh lag of the kind #198780 <#198780> documents. Practical next steps: - Verify the From: author email on 850e4af via .patch and confirm it's an exact match. - If it's exact and still missing after 24h, open a GitHub Support ticket referencing #198780 <#198780> with the commit SHA — that thread records support forcing a manual graph re-index for this same symptom. — Reply to this email directly, view it on GitHub <#206099?email_source=notifications&email_token=AFMZTY5N2NVRKKFJLUCVQIT5MNPNFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGAZDGMZSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18202332>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFMZTY7NZCIMGHL3BKJ2LU35MNPNFAVCNFSNUABIKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TCMBXGA3TCNJUUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AFMZTY55GUYIL2NZ7VDMR235MNPNFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGAZDGMZSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/AFMZTY7SK5Z4YQJF3UBXZVD5MNPNFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGAZDGMZSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>