Issue #3391 open

Repository commit and follower statistics are wrong on repository search and profiles (BB-2590)

Mateusz Heleniak avatarMateusz Heleniak created an issue

In such cases commit count include only commits pushed to repository after migration to BitBucket.

This bug occurs at https://bitbucket.org/repo/mine

Comments (31)

  1. Mateusz Heleniak
    • changed status to open

    Yes problem still persists. For example for EstrisaAssets imported from GitHub commit count on this page is 1 (this one was pushed after migration to BitBucket) although this repo contains 100 commits.

  2. Johannes Dewender

    This is still an issue. Example: https://bitbucket.org/repo/all?name=epydoc

    Epydoc-m was imported from github and should have > 1 k commits. However, none are displayed in the search result. https://bitbucket.org/JonnyJD/epydoc-m/changesets


    Another example: https://bitbucket.org/repo/all?name=musicbrainz

    https://bitbucket.org/JonnyJD/musicbrainz-isrcsubmit/changesets (55 commits, displayed as 0 in search)

    https://bitbucket.org/hangy/ikulo/changesets (23 commits, displayed as 0 in search)

    https://bitbucket.org/adrian/beets/changesets (979 commits, displayes as 2824 in search)

    Note that hangy/ikulo is a hg repository (not imported from github) and the repository is created 2008 (not just now). There are also commit counts that are too high (beets example).


    This is not just a minor presentation bug, since the number of commits is an aspect used to find active and/or big projects.

  3. Johannes Dewender

    epydoc-m now shows up with 4 commits, that is still off by 1500 commits. No clue why the count is 4 now.

    Additionally, the number of followers is not accurate. In https://bitbucket.org/repo/all?name=epydoc the number of followers for neeraj is listed as 5, but there are only 2 followers.

    Listing these stats in searches was one big thing where bitbucket was supposed to be better for open source projects than github, where you only get stats listed for the root, not for the forks.

  4. greku

    The number of commits on the search page should be the correct total number of commits of the repo. Otherwise, the sorting by "commit count" is pretty unmeaningful.

  5. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.