-
-
Notifications
You must be signed in to change notification settings - Fork 608
Ranged copy hash #1244
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
Comments
do you want all the commits listed in a comma-separated way or some |
The former is okay, the latter is a nice topping on top. |
well the one is fundamentally different to the other :) |
IMO reasonable approach would be space-separated commits unless they are selected in turn. This would allow both |
@remique fine by me. are you up for making it a PR? ;) |
Sure, working on it 👍 |
Is your feature request related to a problem? Please describe.
Cherry picking is a daily occurence for my work, and it would usually involve a lot of commits needing to be picked, often 1, but often 10-20 commits as well.
Describe the solution you'd like
It would be nice if we can do a commit selection and have the copy hash shortcut copy the range.
Describe alternatives you've considered
Yes, I could just do a copy and paste of every single commits I want picked, however that's not fast and convenient.
Additional context
None.
The text was updated successfully, but these errors were encountered: