pagure

#4232 Pagure treats non-new commits to any user fork as 'activity'
Opened by adamwill. Modified

Open
Close Issue

Look, for instance, at my activity for 2018-03-05. You'll see entries like this:

"

adamwill committed on pfrields/pagure#8a161a97f98fcb7a65ba1fb0beead800db21e0be

"

It doesn't really make any sense to treat me as having suddenly performed a bunch of "activity" just because pfrields forked Pagure and Pagure has some commits from me in it.

Should we drop all the activities on forks then and thus only count them once they have been merged?

Metadata Update from @pingou:
- Issue tagged with: bug

not sure, that kinda 'feels' right? like, forks are pretty much always going to turn into pull requests and/or commits to master and count as activity anyway, right?

It's entirely possible for long-lived forks to exist. Not counting that activity is a disservice to people who are working from a long-term fork that way.
Metadata
None

bug

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.