That's a perfectly fine solution, but not exactly what I want. With this solution I would have to keep a list of repositories up to date. And in order to update my data I would always need to clone every repository, run the command and put all numbers together.
I like automation, so I looked for a different solution.
Fair enough. I wouldn't consider having a clone of the repo to be a blocker. You could very easily automate the cloning, reporting, deleting of a repo.
That's true. A big advantage of this solution over, let's say a self written post-commit hook, is the past. It doesn't matter when you start collecting this data, thanks to Git you will have data about yourself from the past. With a post-commit hook that's not the case.
I'm still not sure what's the best way to go, but thanks for your comments!
Comments
That's a perfectly fine solution, but not exactly what I want. With this solution I would have to keep a list of repositories up to date. And in order to update my data I would always need to clone every repository, run the command and put all numbers together.
I like automation, so I looked for a different solution.
Fair enough. I wouldn't consider having a clone of the repo to be a blocker. You could very easily automate the cloning, reporting, deleting of a repo.
That's true. A big advantage of this solution over, let's say a self written post-commit hook, is the past. It doesn't matter when you start collecting this data, thanks to Git you will have data about yourself from the past. With a post-commit hook that's not the case.
I'm still not sure what's the best way to go, but thanks for your comments!