Heatmap not showing migration activity #9928

New Issue

GiteaMirror · 2025-11-02T08:53:18-06:00

GiteaMirror commented

2025-11-02 08:53:18 -06:00

Originally created by @alpsware on GitHub (Dec 5, 2022).

Description

When migrating an existing GitHub repository into Gitea, the heatmap and feed on the user dashboard are not showing this activity. When accessing the heatmapdata via the API, it also is not showing this activity there.

Gitea Version

1.17.3

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Selfhosting via official docker image

Database

MySQL

Originally created by @alpsware on GitHub (Dec 5, 2022). ### Description When migrating an existing GitHub repository into Gitea, the heatmap and feed on the user dashboard are not showing this activity. When accessing the heatmapdata via the API, it also is not showing this activity there. ### Gitea Version 1.17.3 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Selfhosting via official docker image ### Database MySQL

GiteaMirror added the type/enhancement label 2025-11-02 08:53:18 -06:00

GiteaMirror commented

2025-11-02 08:53:18 -06:00

@KazzmanK commented on GitHub (Dec 7, 2022):

As I`m still waiting for next stable release before migrating to Gitea , updated heatmap and commit activity on adopting unadopted repositories would be welcome!

@KazzmanK commented on GitHub (Dec 7, 2022): As I`m still waiting for next stable release before migrating to Gitea , updated heatmap and commit activity on adopting unadopted repositories would be welcome!

GiteaMirror commented

2025-11-02 08:53:18 -06:00

@lunny commented on GitHub (Dec 8, 2022):

I'm afraid it's very difficult to migrate all those actions in that repository. But of course we can generate commit actions according the commits history, generate issue/comment actions according migrated issues/comments. But is that necessary? Or should we have an option in migration UI to let users chose?

@lunny commented on GitHub (Dec 8, 2022): I'm afraid it's very difficult to migrate all those actions in that repository. But of course we can generate commit actions according the commits history, generate issue/comment actions according migrated issues/comments. But is that necessary? Or should we have an option in migration UI to let users chose?

GiteaMirror commented

2025-11-02 08:53:19 -06:00

@alpsware commented on GitHub (Dec 8, 2022):

To show all previous activity of an adopted repository in gitea would be a nice enhancement yes. I would prefer to have an option to choose this in the migration UI.

But the origin of this issue was that the migration of a repository itself is not showing in the history heat map. That is, in my opinion, a bug. We set gitea up freshly and the first repository we created was from a migration. Then we did not saw any activity of this migration in the heat map, that's how this was discovered.

@alpsware commented on GitHub (Dec 8, 2022): To show all previous activity of an adopted repository in gitea would be a nice enhancement yes. I would prefer to have an option to choose this in the migration UI. But the origin of this issue was that the migration of a repository itself is not showing in the history heat map. That is, in my opinion, a bug. We set gitea up freshly and the first repository we created was from a migration. Then we did not saw any activity of this migration in the heat map, that's how this was discovered.

GiteaMirror commented

2025-11-02 08:53:19 -06:00

@KazzmanK commented on GitHub (Dec 8, 2022):

So, you need to map git commit authors to existing Gitea users and create activity entries.
If no user mapping occurs - so there will be gaps in activity?
Currently commit history has clickable authors for existing users and grayed for non existing. After creating such user - it becomes clickable in commit history.
So, if it is possible to follow same logic in activity

non-existing user-name may be grayed here too? But as I understand - activity heatmap is a per-user UI, so , ultimately, if I have already imported repository, and after that I create missing user, you will have to query all the existing repositories and extract user activity during user creation.

@alpsware , you have expected a log line stating "Repository migrated"?

@lunny , importing Issues records can be really challenging. Some sources support issues, others are not, others support exclusive features like referencing code lines with outstanding visualizations.

@KazzmanK commented on GitHub (Dec 8, 2022): So, you need to map git commit authors to existing Gitea users and create activity entries. If no user mapping occurs - so there will be gaps in activity? Currently commit history has clickable authors for existing users and grayed for non existing. After creating such user - it becomes clickable in commit history. So, if it is possible to follow same logic in activity ![image](https://user-images.githubusercontent.com/13328513/206410905-24b960fe-ebfa-4c7f-9056-2d18fbd5bcd8.png) non-existing user-name may be grayed here too? But as I understand - activity heatmap is a per-user UI, so , ultimately, if I have already imported repository, and after that I create missing user, you will have to query all the existing repositories and extract user activity during user creation. @alpsware , you have expected a log line stating "Repository migrated"? @lunny , importing Issues records can be really challenging. Some sources support issues, others are not, others support exclusive features like referencing code lines with outstanding visualizations.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#9928