Contribution graph did not rebuild after adding a verified email - 6 consecutive days still show 0

[iceblyte]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Profile

Body

What are you trying to do?​
Get my 2026 contribution graph to count commits that already exist on the
default branch of my own repositories.

What did you expect to happen?​
On Nov 5 I added and verified iceblyte@qq.com as a commit email (it is now my
primary email). The docs say "your contributions graph will be rebuilt
automatically when you add the new address", so I expected the earlier days
authored with that address to be attributed retroactively.

What happened instead?​
Commits pushed after Nov 5 are counted. Nothing before that date has been
re-attributed - 4 days later, six consecutive days still show 0 contributions:

date	commits on default branch	graph shows
2026-10-29	79	0
2026-10-30	56	0
2026-10-31	14	0
2026-11-01	38	0
2026-11-02	28	0
2026-11-03	20	0

Beyond those 6 days the yearly total is also short: 8,242 default-branch
commits authored with a verified email vs 7,475 shown on the graph (~770
missing, e.g. 2026-08-25 47 vs 7, 2026-08-31 64 vs 25, 2026-09-30 36 vs 8).

Things I already ruled out:

• the repositories are standalone copies, not forks (forks never count)
• the commits are on each repo's default branch (main)
• "Include private contributions" is on and works: 2026-11-08 shows exactly 8,
  equal to the 8 commits in my private repo that day
• I waited well past the documented 24 hours
• I did not rewrite history or force-push anything

Any links/screenshots?​
Example commits (.patch "From:" line shows iceblyte@qq.com):
iceblyte/chapter-trail@5e2f11f
iceblyte/tab-tray@84f1d58
iceblyte/squirl@973a018

Screenshot of the gap:

My question: is there a supported self-service way to trigger a contribution
data rebuild, or is the "automatic rebuild on adding an email" path known to
skip commits that were pushed before the address was added?

[100rootrain]

I looked at your public repos, and the gap lines up exactly with your email switch:

• Oct 27–28: commits are authored with 2624507601@qq.com, which was presumably already on your account, and they're counted (104 and 55 on the graph).
• From Oct 29: commits switch to iceblyte@qq.com, which you added on Nov 5. Every day from then until Nov 5 shows 0. Nov 4 is in the gap too: tab-tray has 8 commits that day with the same email.

The commit pages now link those commits to your account (the author resolves to iceblyte), so the email association itself works. It's only the retroactive recount, the "graph will be rebuilt automatically" step, that never ran. New commits are counted normally because they're processed as they're pushed.

Is there a self-service rebuild?

Not that I know of. Adding an email is the only documented trigger. Two things people have tried, which I'd avoid or not count on:

• Removing and re-adding the email: don't. Several people who did this recently ended up with more history missing, not less (Historical contribution graph not fully restored after re-adding my verified email #211738, Historical contributions missing after verified email transfer: expected rebuild behavior? #211895, and a report in [Incident]: Profile rendering issues affecting GitHub profiles #203416 still unresolved after two weeks).
• Pushing a new commit to the repo: one person in [Incident]: Profile rendering issues affecting GitHub profiles #203416 saw a repo's history come back after a push, but it didn't work for their other repo. In your case, chapter-trail got a push at 07:19 UTC today, and its Oct 30–31 commits still aren't counted, so I wouldn't rely on it.

This looks like part of the ongoing incident in #203416, which explicitly lists "Contribution graphs not accurately reflecting commits". GitHub hasn't given a fix timeline there. I'd add your case to that thread, since that's where staff are tracking it. Your before/after table and the email boundary make it a very clear report. Note that at least one person's Support ticket for this was closed with a redirect to Community.

On the earlier short days (Aug 25, Aug 31, Sep 30), it's worth checking which email those commits used, e.g. git log --since=2026-08-25 --until=2026-08-26 --format='%ae' | sort | uniq -c. If they're also iceblyte@qq.com, it's the same missing rebuild, and they should come back when it eventually runs.

[iceblyte]

Closing the loop for anyone arriving from search: this matches the ongoing incident tracked in #203416 ("Contribution graphs not accurately reflecting commits"). Staff are collecting cases there and there is no ETA yet.

Also worth recording: pushing an empty commit to the default branch does NOT force a re-index of past commits - I tested it, no effect.