Change Details

I'd like to see where the most "churn" happens in a code base over time. If change sets are categorized ("bugfix", "feature", ...) then you can get a useful insights in the code base. For example, looking at what files have the most "bugfixes" over time could point out that there is a problem in the design, readability, etc. of that file / subsystem.

I'd like to see where the most "churn" happens in a code base over time. If change sets are categorized ("bugfix", "feature", ...) then you can get a useful insights in the code base. For example, looking at what files have the most "bugfixes" over time could point out that there is a problem in the design, readability, etc. of that file / subsystem. Is something like this in Phabricator?

I'd like to see where the most "churn" happens in a code base over time. If change sets are categorized ("bugfix", "feature", ...) then you can get a useful insights in the code base. For example, looking at what files have the most "bugfixes" over time could point out that there is a problem in the design, readability, etc. of that file / subsystem. Is something like this in Phabricator?