• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 3.2
    • Git
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently the Cherry Pick command also commits immediately. Would it be possible to optionally cherry-pick and not commit (I believe this is the equivalent of "git cherry-pick -n <SHA1>"?

      Thanks.

            [SRCTREE-1026] Support cherry-pick without commit

            When will this release be?

            I have been waiting eagerly for many years for this feature.

            SourceTree is still the best GUI for Git!

            Andre Jacobs added a comment - When will this release be? I have been waiting eagerly for many years for this feature. SourceTree is still the best GUI for Git!

            Double great!

            So I can remove my Custom Action

            Michael Steiger added a comment - Double great! So I can remove my Custom Action

            It will ship in the next update for it as well.

            Brian Ganninger (Inactive) added a comment - It will ship in the next update for it as well.

            Great!

            Any plans to also add this to the Windows version of Sourcetree?

            Michael Steiger added a comment - Great! Any plans to also add this to the Windows version of Sourcetree?

            FYI: you can amend a commit message (that hasn't been pushed) in Sourcetree, there's a menu item in the Commit Options… popup in the message editor. It populates with the last commit's message when clicked and if you commit it after editing will just change the text as you did on the command line. (this experience could be better, but it works for now)

            Brian Ganninger (Inactive) added a comment - - edited FYI: you can amend a commit message (that hasn't been pushed) in Sourcetree, there's a menu item in the Commit Options… popup in the message editor. It populates with the last commit's message when clicked and if you commit it after editing will just change the text as you did on the command line. (this experience could be better, but it works for now)

            Hi folks,

            Just wanted to let everyone know we are listening In the next minor update for each platform we're adding a new cherry pick dialog. Here's the layout (mockup, not in app):

            Thank you for your patience and workarounds in the meantime!

            Brian Ganninger
            Principal Developer, Sourcetree

            PS: To answer the obvious followup question - it should enter beta by the end of this month and then ship after a typical round of beta testing.

            Brian Ganninger (Inactive) added a comment - - edited Hi folks, Just wanted to let everyone know we are listening In the next minor update for each platform we're adding a new cherry pick dialog. Here's the layout (mockup, not in app) : Thank you for your patience and workarounds in the meantime! Brian Ganninger Principal Developer, Sourcetree PS: To answer the obvious followup question - it should enter beta by the end of this month and then ship after a typical round of beta testing.

            In my case I just wanted to edit the commit message to include some more details about the cherry pick. To get around this I would let Sourcetree cherry pick what I wanted and commit, then go in with the git command line and edit the last commit message. The workaround for this is detailed below.

            1. Open git bash to git repository
            2. Enter 'git commit --amend'
            3. This will open up an editor where you can edit the last commit message
            4. After closing the editor, the edit commit message will show up in Sourcetree

            Not the greatest solution as having this integrated into Sourcetree would be great but is a workaround if you just need to edit the commit message.

            Kendall Hertzler added a comment - In my case I just wanted to edit the commit message to include some more details about the cherry pick. To get around this I would let Sourcetree cherry pick what I wanted and commit, then go in with the git command line and edit the last commit message. The workaround for this is detailed below. Open git bash to git repository Enter 'git commit --amend' This will open up an editor where you can edit the last commit message After closing the editor, the edit commit message will show up in Sourcetree Not the greatest solution as having this integrated into Sourcetree would be great but is a workaround if you just need to edit the commit message.

            Can we please get any update on this? Thanks.

            rbukovansky added a comment - Can we please get any update on this? Thanks.

            Would still be nice to have as a feature, but thank you Roger for the workaround, works great

            Christian Gassner added a comment - Would still be nice to have as a feature, but thank you Roger for the workaround, works great

            This workaround worked for me, but this would be nice to have integrated into SourceTree

            eyesofjeremy added a comment - This workaround worked for me, but this would be nice to have integrated into SourceTree

            anacrolix added a comment -

            SourceTree get stuck in the dialog when attempting to create this (or any) custom action on OSX.

            anacrolix added a comment - SourceTree get stuck in the dialog when attempting to create this (or any) custom action on OSX.

            Thx Roger, that I did not think of this . But then again, it should be easy to implement it into the client. Thanks!

            Kevin Smets added a comment - Thx Roger, that I did not think of this . But then again, it should be easy to implement it into the client. Thanks!

            I defined a custom action for this, it does the job quite nicely.

            Roger Barnes (Inactive) added a comment - I defined a custom action for this, it does the job quite nicely.

            Same here, reverted to Tower just for this.

            Kevin Smets added a comment - Same here, reverted to Tower just for this.

            Pierre Renaux added a comment - - edited

            Me too, I have to use GitExtensions to cherry pick because of this.

            Pierre Renaux added a comment - - edited Me too, I have to use GitExtensions to cherry pick because of this.

            Putting in another request for this. It would definitely be a great improvement.

            Michael DeMille added a comment - Putting in another request for this. It would definitely be a great improvement.

            Please consider fixing this. The biggest reason I might cherry pick something is to take part of a commit or change the comment... Auto commit is a real pain.

            Joseph Watson added a comment - Please consider fixing this. The biggest reason I might cherry pick something is to take part of a commit or change the comment... Auto commit is a real pain.

            Ditto, forces me to switch to SmartGIT. Essential to be able to cherry pick to the working copy then commit subsequently with an altered comment if required.

            Ian Cartland added a comment - Ditto, forces me to switch to SmartGIT. Essential to be able to cherry pick to the working copy then commit subsequently with an altered comment if required.

            Alex Sinm added a comment -

            Currently its the only feature i'm missing, forces me to switch to Tower!

            Alex Sinm added a comment - Currently its the only feature i'm missing, forces me to switch to Tower!

              bganninger Brian Ganninger (Inactive)
              mikehatfield mikehatfield
              Votes:
              76 Vote for this issue
              Watchers:
              46 Start watching this issue

                Created:
                Updated:
                Resolved: