-
Notifications
You must be signed in to change notification settings - Fork 14
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
Support creating & applying patches #539
Comments
Does anybody know if there is an update on this issue? Is it on the roadmap? |
I ended up making the following commands (save them in
|
Hi all, This has been added in Sublime Merge 2075 (development build), and will be added to the next stable build. If you have any feedback, feel free to add to it here! Cheers, |
@dpjohnst This is great, thanks. One question, maybe I'm just holding it wrong, but I can't seem to find a way to create a patch with multiple files? I can right click a file in the file browser and the file tab bar and then make an individual patch. Is there no way to select multiple files to create a patch and/or create a patch from the staged and/or unstaged changes? |
Hi @JustSid, Thanks for reaching out - currently we don't support multi-select for files. Kind regards, |
Problem description
A common workflow for transferring a work-in-progress between machines is to create a "patch" file on one machine, then apply it on another. As described in this Stack Overflow discussion, the way you'd do this from the command line is:
$ git diff [--cached] [--binary] > mypatch.patch
$ git apply mypatch.patch
This is different from #215, because the desire is to not have to create a commit (like
git format-patch
requires).Preferred solution
I rather like the way SourceTree does this, where you enter the "create a patch" UI and can choose the files to be included in the patch, the destination, etc. Alternatively, a much simpler alternative would be Command Palette actions for:
(each of which would take the path to the patch file)
Screenshots
Here's the UI SourceTree uses for choosing the files to include in a patch:
The text was updated successfully, but these errors were encountered: