Activity is not visible for migrated repositories #1807

axbg commented 2025年03月05日 17:45:03 +01:00

Comment

Hello, I've just migrated my repositories from GitHub.

I tried first using the migrate endpoint, and everything was fine, but I observed that the contributions inside the repo were not reflected in the Contributions panel on Codeberg.

I also tried to migrate a repo manually, by changing the target origin and pushing all the code at once.

While the commits are correctly shown and the username (identical, in my case) is correctly linked as "committer", the activity in the Contributions panel is still not visible.

I guess that the problem could be related to how Codeberg tracks the contributions, which might be separated from the commits themselves.

I know it's not such a big issue, but I was wondering if any "fix" for this is currently available and, if not, what it would imply to develop something to cover it.

### Comment Hello, I've just migrated my repositories from GitHub. I tried first using the _migrate_ endpoint, and everything was fine, but I observed that the contributions inside the repo were not reflected in the Contributions panel on Codeberg. I also tried to migrate a repo manually, by changing the target origin and pushing all the code at once. While the commits are correctly shown and the username (identical, in my case) is correctly linked as "committer", the activity in the Contributions panel is still not visible. I guess that the problem could be related to how Codeberg tracks the contributions, which might be separated from the commits themselves. I know it's not such a big issue, but I was wondering if any "fix" for this is currently available and, if not, what it would imply to develop something to cover it.

fnetX commented 2025年03月06日 23:21:27 +01:00

The Git repo contains no information on who pushed the content and when. This metadata is only recorded while a push is happening. For example, if you authored five commits, you could have pushed all of them at the same time, or all of them one-by-one. You could have pushed them only weeks after authoring them etc. Or you could have sent them to a friend who pushed them instead.

It is currently not possible to migrate the activity from GitHub or similar platforms. It would require gathering all that information from their APIs, which might require a lot of effort and is generating a lot of load on both sides, requires dealing with rate-limits etc. And the benefit is comparatively low.

The Git repo contains no information on who pushed the content and when. This metadata is only recorded while a push is happening. For example, if you authored five commits, you could have pushed all of them at the same time, or all of them one-by-one. You could have pushed them only weeks after authoring them etc. Or you could have sent them to a friend who pushed them instead. It is currently not possible to migrate the activity from GitHub or similar platforms. It would require gathering all that information from their APIs, which might require a lot of effort and is generating a lot of load on both sides, requires dealing with rate-limits etc. And the benefit is comparatively low.