Commits Lost After Project Rename

Bug #1674092 reported by Yuval Brik
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Stackalytics
Fix Released
Undecided
Yuval Brik

Bug Description

After project rename (i.e Smaug -> Karbor, Nimble -> Mogan, etc) all git related stats (commits, lines of code) that were done before the rename are lost. Only changes made after the rename are counted.
Note: projects added the previous name to 'aliases' in default_data.json

Revision history for this message
Yuval Brik (jhamhader) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to stackalytics (master)

Reviewed: https://review.openstack.org/447298
Committed: https://git.openstack.org/cgit/openstack/stackalytics/commit/?id=57de5f7ba318a11fa5e5fb3a3026a500b3c07968
Submitter: Jenkins
Branch: master

commit 57de5f7ba318a11fa5e5fb3a3026a500b3c07968
Author: Yuval Brik <email address hidden>
Date: Mon Mar 20 17:52:07 2017 +0200

    Update commit records with module aliases

    When repos are renamed, commit records with the old name remain and are
    not counted for the new repo name.
    During post-process, rename the module name of all commits with the old
    name, to be the new name.

    Change-Id: I8684c5a1949ea916768bce9441d011325d079ad4
    Closes-Bug: #1674092

Changed in stackalytics:
status: New → Fix Released
Yuval Brik (jhamhader)
Changed in stackalytics:
assignee: nobody → Yuval Brik (jhamhader)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.