GitHub Activity Missing After GitLab Repo Migration

[oscrwebr]

🏷️ Discussion Type

Bug

Body

Hi everyone,

I recently migrated a GitLab repository to GitHub, preserving its full commit history. However, despite waiting over a week, my historical contributions still aren't appearing on my GitHub profile's contribution graph.

I previously contacted GitHub Support, but my ticket was closed and I was directed to ask here instead.

Repository: http://github.com/oscrwebr/data-trust-engine

Example commit: oscrwebr/data-trust-engine@1120060e

What I've already verified

• Email attribution: My historical commits use my university email (WebsterO1@cardiff.ac.uk), which I've added and verified on my current GitHub account.
• Author recognition: Clicking my name on a historical commit correctly links to my GitHub profile (oscrwebr).
• Default branch: The repository's default branch is main.
• Commit history: I've confirmed using git merge-base --is-ancestor that my historical commits are included in origin/main (exit code 0).
• Repository visibility: The repository is public and is not a fork.
• Original dates: The commits retain their original timestamps, including commits from April 2026.
• Waiting period: It's been over a week since the migration and email verification.

The issue

Despite satisfying these requirements, my historical commits aren't being reflected in my contribution graph.

The repository correctly displays its commit history, and GitHub recognises me as the author, so I'm unsure why the contributions aren't being counted.

Has anyone encountered this when migrating a repository from GitLab to GitHub?

Is there an additional requirement for imported Git history, or a way to trigger GitHub to recalculate contributions?

I'd appreciate any suggestions. 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. ⭐