Contribution graph not reflecting commits after fork migration

[Kiki-byte-io]

🏷️ Discussion Type

Bug

Body

Hi everyone,

I'm having an issue with my GitHub contribution graph for my public repository, [Kiki-byte-io/HoneyWatch](https://github.com/Kiki-byte-io/HoneyWatch).

I migrated the project from a fork to a standalone repository while preserving its Git history. My profile's Contribution activity shows three commits to HoneyWatch dated October 7, 2026, but the contribution calendar doesn't appear to reflect them as expected. It's been more than 72 hours.

I've checked the following:

• The repository is public and is no longer a fork.
• main is the default branch, and all three commits are present on it.
• My commit email (kiki2freakyo@gmail.com) is verified and associated with my GitHub account.
• The author dates and commit dates match.
• The commits appear in my profile's Contribution activity.

Affected commits:

• [48b4e96](Kiki-byte-io/HoneyWatch@48b4e96)
• [6579956](Kiki-byte-io/HoneyWatch@6579956)
• [79cb1ae](Kiki-byte-io/HoneyWatch@79cb1ae)

Has anyone experienced this after migrating a repository from a fork to a standalone repository? Is there another eligibility check or refresh step I should investigate?

Thanks!

[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. ⭐

[Kiki-byte-io]

Guys I clicked the year 2026 again and it refreshed. Like Github is so stupid. I checked everything for hours and all it needed was a fucking me clicking on year 2025 and then back to 2026. URGHHHHHHHHH

[Sagargupta16]

They are on the graph now. At 13:55 UTC today the public calendar for Kiki-byte-io shows "4 contributions on October 7", and the GraphQL contributions data lists Kiki-byte-io/HoneyWatch with 3 commits on 2026-10-07. The fourth contribution that day is creating the repository, which counts on its own.

Why it lagged: the three commits are dated 10:44 to 10:47 UTC on October 7, but HoneyWatch as a standalone repository was created at 11:11 UTC, 24 minutes later. While they only existed in the fork they were ineligible ("Commits made in a fork will not count toward your contributions"). When you pushed them to main of the new repo they became eligible, but the calendar is recomputed asynchronously rather than at push time, and in your case that took longer than the "up to 24 hours" the docs promise. Nothing on your side was wrong: email, default branch, dates and fork status all check out.

You can confirm without waiting on the UI:

gh api graphql -f query='{ user(login:"Kiki-byte-io"){ contributionsCollection(from:"2026-10-07T00:00:00Z", to:"2026-10-07T23:59:59Z"){ commitContributionsByRepository{ repository{ nameWithOwner } contributions(first:5){ nodes{ occurredAt commitCount } } } } } }'

One thing to keep in mind going forward: commits on hardening/telemetry-audit will not count until they land on main, since only the default branch (and gh-pages) is counted.