Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add suggestion on how to resolve spotted issues #69

Open
ykoehler opened this issue Mar 24, 2021 · 1 comment
Open

Add suggestion on how to resolve spotted issues #69

ykoehler opened this issue Mar 24, 2021 · 1 comment

Comments

@ykoehler
Copy link

As an example, when the biggest blob is found, git-sizer could suggest how to remove it. There is a tool out there named git-forget-blob which could be used to solve the issue if the blob is to be found to be a mistake.

For example in our case, someone had committed/pushed a cscope.out in their own branch.

When there are possible solution like this, providing a "suggestion" on how to proceed next, would be awesome.

@mhagger
Copy link
Member

mhagger commented Mar 24, 2021

It's an interesting idea. I don't think I'd want git-sizer itself to try to explain possible next steps, since they can be pretty complicated and also have implications like invalidating signed tags and SHA-1s in issue comments that we'd want to make users aware of. But I can imagine git-sizer outputting links to longer-form articles or maybe to the instructions that go along with tools like git-filter-branch or BFG that they might want to use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants