Advice for alleviating found issues? about git-sizer HOT 1 CLOSED

The project README (which is visible on the project page) gives a lot of generalized tips for dealing with various problems that can be detected by git-sizer. Though I agree that it's not always obvious from the git-sizer output which of these problems the repository is suffering from. We could explain that better.

It would also be thinkable for the program (perhaps when some new --advice option is specified) to try to summarize the problems that it found at a higher level of abstraction and to emit some possible recommendations for how to fix it.

Most fixes would involve rewriting the project's history, for example using git filter-branch or the BFG repo cleaner. Unfortunately, rewriting history is somewhat fiddly and also rather disruptive if the project has many collaborators. Part of my hope with git-sizer is that it helps people detect problems before they are so critical that they require a history rewrite.

I'm closing this issue because it's not actionable in its current form. If you have more specific requests or ideas, feel free to reopen or to open a new issue or PR.

from git-sizer.