Skip to content
Discussion options

You must be logged in to vote

Churn as the first filter is sensible, but I'd add one derived signal: author diversity on the same path. A file with 40 commits from one person is well owned even if nobody is in CODEOWNERS. A file with 12 commits from six people and no clear owner is where reviews are weakest — that's the one to fix first.

You can get both numbers locally without any tooling beyond Git:

# churn: most-changed paths in the last year
git log --since='1 year ago' --name-only --pretty=format: \
  | sed '/^$/d' | sort | uniq -c | sort -rn | head -40

# for a candidate path: how many different authors touched it
git log --since='1 year ago' --format='%ae' -- path/to/file | sort -u | wc -l

# account for renames
…

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
1 reply
@Tomosu-AI
Comment options

Comment options

You must be logged in to vote
1 reply
@Tomosu-AI
Comment options

Answer selected by Tomosu-AI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Repositories The core of version-controlled code storage Question Ask and answer questions about GitHub features and usage Welcome 🎉 Used to greet and highlight first-time discussion participants. Welcome to the community! source:ui Discussions created via Community GitHub templates
3 participants