-
Notifications
You must be signed in to change notification settings - Fork 71
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 feature to generate one fixup per commit. #91
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry that my primary feedback is "i disagree with the structure of the refactor", i know that's the most annoying sort of feedback i could have given.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, that's the arrangement i had in mind
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm other than this last comment. let me know if you still want to try mempack on this pr, otherwise i'll merge after this one is addressed
oh and also, the new test is failing so you'll have to figure out what's going on there. looks like something trivial related to the new repo having no configured user |
0096d28
to
e16fcff
Compare
This means that all hunks meant to be fixed up into the same commit will be grouped into a single commit, rather than multiple ones. In order to not break the workflow of others, we choose to make this an option rather than the default. Moreover, folks can `alias git-absorb="git-absorb --one-fixup-per-commit"` if they wish to always use this option, and not have to type it out.
@tummychow I squashed away the commits to clean the history up a bit. I think I will follow-up with improving the tests since it's taking longer than I expected |
Also thank you for the quick turnaround! |
no problem, thanks for implementing all the requested changes. will probably cut a release for this later in the week |
Thanks for implementing this feature! Any reason the new |
There's an explanation in the first commit message:
I will let @tummychow decide whether it should become the default in a later release or not. |
yeah i want to let it bake for a while, given the amount of code getting moved around. i would accept a pr to add a git config option for it though |
This is my attempt at implementing the feature request from #19.
I would suggest reviewing the changeset commit by commit, since I made sure to split the work into logical chunks: refactor, add feature, tests, and so on.
Closes issue #19.