Collecting trends retroactively #118
martinrleon
started this conversation in
General
Replies: 2 comments
-
might be somewhat related: git punchcard -p month/wday -- --since=1.year --author="Casper" ![]() |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Thank you for the git-fame tool, it’s a great resource for me.
I want to develop a dashboard of metrics-over-time using your tool. What is the best approach for collecting ‘past snapshots’ - meaning, if I want to see the trends in metrics for the past year, month over month, what is the best approach?
I started using ‘--since’ and ‘--until’ to kind of partition the results as if they were being collected over time, one month at a time, starting from a ‘shallow’ clone going back to include only 1 year of commits. So it would be '--since 2025-07-01’ '--until 2025-07-31’, then the same for 2025-06, 2025-05, 2025-04, and so on until 2026-06 to catch me up to the current month.
The collected data monthly snapshots (repo totals / contributor totals in json) would be captured in a DB and then graphs would show trends in commits, files, hours, etc, either at the individual level or at the repo level month-by-month.
My biggest concern is to accurately capture and represent these trends - does the above approach look reasonable / correct?
Any suggestions appreciated.
Beta Was this translation helpful? Give feedback.
All reactions