Inlucde activity from mirrored repos into activity graph #9370

New Issue

GiteaMirror · 2025-11-02T08:36:44-06:00

GiteaMirror commented

2025-11-02 08:36:44 -06:00

Originally created by @MarcelCoding on GitHub (Aug 8, 2022).

Feature Description

I don't quite know the actual behavior.

I think only the activity that actually happens over Gitea is included. It would be nice if also the activity from mirrors/migrations would be included. I don't know if the activity is included if someone different pushed on behalf of you (e.g. interactive rebase, ...), if not this would also be nice.

(low priority)

Screenshots

No response

Originally created by @MarcelCoding on GitHub (Aug 8, 2022). ### Feature Description I don't quite know the actual behavior. I think only the activity that actually happens over Gitea is included. It would be nice if also the activity from mirrors/migrations would be included. I don't know if the activity is included if someone different pushed on behalf of you (e.g. interactive rebase, ...), if not this would also be nice. (low priority) ### Screenshots _No response_

GiteaMirror added the type/proposal type/feature labels 2025-11-02 08:36:44 -06:00

GiteaMirror closed this issue

2025-11-02 08:36:45 -06:00

GiteaMirror commented

2025-11-02 08:36:45 -06:00

@lafriks commented on GitHub (Aug 8, 2022):

it's not really possible as activity is in commits and parsing all commits that have been changed between sync would be quite slow. Also if user registers later on or changes email that historical commit had would still not show up in activity so it would always be inaccurate anyway

@lafriks commented on GitHub (Aug 8, 2022): it's not really possible as activity is in commits and parsing all commits that have been changed between sync would be quite slow. Also if user registers later on or changes email that historical commit had would still not show up in activity so it would always be inaccurate anyway

GiteaMirror commented

2025-11-02 08:36:45 -06:00

@MarcelCoding commented on GitHub (Aug 8, 2022):

The email change thing is a point. But wouldn't it be possible to check this on every push (for the commits in the push) - there is no other location where commit could be changed other than pushes.

@MarcelCoding commented on GitHub (Aug 8, 2022): The email change thing is a point. But wouldn't it be possible to check this on every push (for the commits in the push) - there is no other location where commit could be changed other than pushes.

GiteaMirror commented

2025-11-02 08:36:45 -06:00

@lafriks commented on GitHub (Aug 8, 2022):

yes but commit count can be large (for example initial migration of linux kernel), branches can also be deleted etc. What if user registers in this gitea instance after repository was initially mirrored already?

@lafriks commented on GitHub (Aug 8, 2022): yes but commit count can be large (for example initial migration of linux kernel), branches can also be deleted etc. What if user registers in this gitea instance after repository was initially mirrored already?

GiteaMirror commented

2025-11-02 08:36:45 -06:00

@lafriks commented on GitHub (Aug 8, 2022):

That is also reason why we do not count also in regular repository commit history. If you would push 100 commits that you have been working on for year, you would still have single activity event in your activity graph.

@lafriks commented on GitHub (Aug 8, 2022): That is also reason why we do not count also in regular repository commit history. If you would push 100 commits that you have been working on for year, you would still have single activity event in your activity graph.

GiteaMirror commented

2025-11-02 08:36:46 -06:00

@MarcelCoding commented on GitHub (Aug 8, 2022):

So only pushing is an activity event and not commiting?
Anyways thanks for your time and clarification.

@MarcelCoding commented on GitHub (Aug 8, 2022): So only pushing is an activity event and not commiting? Anyways thanks for your time and clarification.

GiteaMirror commented

2025-11-02 08:36:46 -06:00

@lafriks commented on GitHub (Aug 8, 2022):

So only pushing is an activity event and not commiting? Anyways thanks for your time and clarification.

yes

@lafriks commented on GitHub (Aug 8, 2022): > So only pushing is an activity event and not commiting? Anyways thanks for your time and clarification. yes

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#9370