-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
git-imerge: add page #934
git-imerge: add page #934
Conversation
|
||
- Start imerge-based rebase (checkout the branch to be rebased, first): | ||
|
||
`git imerge rebase {{branch_to_rebase_into}}` |
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.
I suggest changing the argument name to branch_to_rebase_onto
, since your branch will end up on top of the other branch; the other branch is not changed.
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.
Sure! as a non-native English speaker, these nuances sometimes elude me :) thanks for the review!
I didn't know about this tldr thing, but it seems useful. I think you've captured the most important Do tldr pages typically mention where commands can be installed from, or include cross-references to the main documentation? But anyway, 👍 thanks for this ✨ |
Yeah, I thought about that too, but it hasn't been the case so far. I suppose the expectation is that when someone tldr's a command, it's because they already know about it, which seems fair. Still, a future "references", "links" or "notes" section is certainly something we should consider. C.f. #785 |
Given the blessing of the tool's author himself, I'll self-merge :) |
👍 |
https://github.com/mhagger/git-imerge
/cc @mhagger