-
-
Notifications
You must be signed in to change notification settings - Fork 216
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
Make a clean git history? #120
Comments
Thank you for the feedback! I will improve my commits. |
Future commits will be squashed before the PR. |
@xandao6 why was the issue closed? There are ~300 commits for ~500 lines of code, which doesn't look good. |
Hey, I would like to work on this issue. Can I be assigned this issue? |
@Pihu1998 it's probably on us, instead of participants. A PR can only update the repository by placing commits on top, and not change the order of commits set earlier. |
Oh, I get it now. Thanks for the information. :D |
@xandao6 @rpotter12 @nileshpatra |
I think nobody |
I will look at this in some days. I'm little busy these days. |
i want to work on this issue |
@arpitasahakundu That's for me. :) |
Currently the git history seems very cluttered, making it difficult to keep a track of changes.
For example ; this, this, this et. al.
IMO, smaller changes can be squashed to get a sane git history.
The text was updated successfully, but these errors were encountered: