-
Notifications
You must be signed in to change notification settings - Fork 165
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
Unpleasant commit history #89
Comments
Hi, Could you please clean the git history dear @reganto? |
Hi dear @bobycloud There is an interactive rebase solution for this situation but with that solution we lose a lot of commits. I'm curious to know if you have any experience of cleaning up git history without losing commits? |
@reganto , If the commits are redundant and useless, Losing them won't hurt anyone. I believe it might actually benefit us too. |
Dear @SepehrRasouli Honestly, I don't have a clear idea about this. But I can think of people who made their first open source contribution to this repository. They might later want to refer to their first contribution, and if we consider their PR as their signature, I don't think it would be ethical to erase that signature. |
Your reasoning is very ethical and I completely understand it. |
Hi, I realized that git history is a little bit dirty
suggestions:
Squash and mergeBest Regards
Reganto
The text was updated successfully, but these errors were encountered: