newren/git-filter-repo

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

Open

#392 opened on Sep 12, 2022

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Python (674 forks)batch import
enhancementgood first issue

Repository metrics

Stars
 (6,745 stars)
PR merge metrics
 (Avg merge 44d 2h) (1 merged PR in 30d)

Description

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?

Contributor guide

Research direction
Investigate the current analyze implementation in git filter repo to understand how it computes blob statistics, then design and implement a new output file (e.g., blob frequency.txt) that lists each blob path and its commit frequency.
Tech stack
python
Domain
clitooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60