Contribution graph stuck mid-rebuild after email re-verification — one private repo never backfills #203457
Unanswered
skubski
asked this question in
Other Feature Feedback, Questions, & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Profile
Body
I'm consolidating two GitHub accounts: keeping
skubski, retiring my old accountkubskse. On 2026-07-23 I moved my work email from the old account toskubskiand verified it, andskubskiwas granted admin collaborator access on the three private repos involved (orgTheBeehiveBE:ITAA-KT3.0,ITAA,ITAA-front).Commit→account linking is correct everywhere. The REST API (
/repos/.../commits?author=skubski) attributes all my historical commits in all three repos toskubski. The problem is only the contribution graph, which never backfilled after the access grant and now appears stuck mid-rebuild.What I've observed, in order:
ITAA-KT3.0jumped from 1 to ~392 commits. The other two repos stayed at zero.ITAA-frontbackfilled its 2025 commits (99).ITAAstayed at zero.ITAA-KT3.0392→328,ITAA-frontdown to 61/99), but the restore after re-verification has been draining extremely slowly and has now been stalled for ~36 hours:ITAA-KT3.0stopped at 346 (expected ~392+),ITAA-frontat 61 for 2025 (expected 99) and 99 for 2026 (expected ~150).Current vs. expected (private repos, org
TheBeehiveBE, measured via the GraphQLcontributionsCollectionAPI):ITAAhas never been picked up by any rebuild cycle, despite correct commit attribution, collaborator access, commits on the default branch, and recent push activity by my account (I pushed a commit to it on 07-28 to make sure there's an activity event).Questions:
I've stopped doing further remove/re-add cycles since each removal instantly de-links everything while the restore takes days. Happy to provide timestamps or repo details privately if a staff member picks this up.
(Note: an earlier duplicate of this post, #203455, was accidentally submitted from a colleague-managed account; it points here now.)
All reactions