newren/git-filter-repo

Have --analyze provide frequency of changes to individual paths as well

Open

#392 建立於 2022年9月12日

在 GitHub 查看
 (7 留言) (0 反應) (0 負責人)Python (6,745 star) (674 fork)batch import
enhancementgood first issue

描述

When using filter-repo --analyze on problematic repos, especially those with a deep history, I often times find that the problematic blobs are the ones that are not necessarily the largest, but those of a medium size that are committed either by an automated system or a common binary being frequently rewritten by users. Is there currently an easy way to output the frequency of blobs committed, if not, would there be interest in having a blob-frequency.txt with the blob name and count?

貢獻者指南

技術棧
python
領域
toolingcli
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic Python knowledgeUnderstanding of git filter repo's analyze
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
Examine the existing analyze code in git filter repo, specifically the functions that generate output files like 'analysis/*.txt'. The feature request asks for a new file 'blob frequency.txt' listing blob names and their commit frequency. Look at the comments in the issue for any maintainer suggestions on implementation approach or data structures. Consider how to efficiently count blob occurrences across commits without excessive memory usage.