newren/git-filter-repo

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

Open

#392 opened on 2022年9月12日

GitHub で見る
 (7 comments) (0 reactions) (0 assignees)Python (6,745 stars) (674 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.