How to create a pull request with selected commits?

[Suresh Sakhare]

Hi,

I am trying to create a pull request with selected commits using latest bitbucket cloud rest API. But it creates a pull request with all commits.

Suppose, I have a branch BXI-01 which has four commits i.e commit1,commit2,commit3 and commit4. How can we create a pull request with commit3 and commit4 only? 

URL: https://api.bitbucket.org/2.0/repositories/suresh2702/test/pullrequests

Data:

{  
   "title":"Testing pull request created fourth time. with single commit ",
   "close_source_branch":true,
   "destination":{  
      "repository":{  
         "type":"repository",
         "name":"test"
      },
      "branch":{  
         "name":"master"
      }
   },
   "state":"OPEN",
   "source":{  
      "repository":{  
         "type":"repository",
         "name":"test"
      },
      "branch":{  
         "name":"BXI-01"
      },
      "commit":{  
         "hash":"e95bc71987c76503657d273aa7afc6209c4014e8"
      }
   },
   "reviewers":[  
      {  
         "username":"xyz"
      }
   ]
}

 UPDATE?

[Suresh Sakhare · Accepted solution]

Hi Guys,

There is no option to create PR with selected commits. If you want to create PR with selected commits you need to create temp branch and do git cherry-pickup commits and raise the PR with temp branch.

[stephenpostscript]

It would be great if Atlassian could make a way to let us just cherry-pick in the PR interface so we don't have to create a branch in these cases. Would save a lot of time.

[Adrian R.]

Yes that would be great please

[Gutte]

That would be amazing!

[Roland]

That would be extremely useful. Is there anyway we can suggest this as a feature?

[Chitra Tatachar]

+1 on this feature please. Just arrived here while wanting to do the same. Would really help in a lot of use cases, with many devs, many branches and many features. Some commits would need to be merged with one main branch and not with others. Also, there are times where the only way we can merge is raising a PR without permission to directly merge to one branch. Also for hotfixes.
Thanks. 

[Sorin]

+1 on this feature. Came here looking a way to do exactly this, would be great to have it

[Speed Franklin]

This would be great so I don't have to break our team's workflow and go to the command line. Thanks

[Swathi Krishnamurthy]

+1.  This is a required feature.

[Giles Hinton]

+1 - this should be a feature out of the box.  TFS does it and has a much nicer interface to review pull requests.

[Justin]

Would love this feature. With multiple devs working against a repos, we find it common place to have multiple commits made (for version protection and code protection) that are not ready for merge to stage or prod. When a pull request is created we have no way currently to cherry pick the commits that are ready to deploy. This limitation leads to multiple branches - one per dev that have to be constantly synchronized overly complicating the dev-ops process. 

[Eduarda Almeida Leao Marques]

+1 to this feature. A lot of work can be saved with this feature!  

[Sharada Ramakrishnan]

+1 to this feature

[Deleted user]

+1 to this feature

[maddy302]

+1 to this feature

[Malgorzata Jesionowska]

+1 to this feature

At times I have a branch for whole epics, but I work on things that are only "seemingly related" (like separate windows). Unfortunately, those 'things' share common assets like textures, which I have to constantly work on, and a texture don' merge at all.

If I have to create a separate branch for each thing I do and all those share common texture, imagine how merging changes on a texture to all those branches would take.

[Damien Minter]

+1 to this feature

[Keshava GN]

+1 to this feature

[Andrew Wagner]

+1 to this feature

[Janeshwar Sritharan]

+1 to this feature

[Gabriel Rabelo]

+1 to this feature

[Nicoleta A_ Soare]

+1 for this feature

[Dean Cox]

+1 for this feature

[Simran]

+1 for the feature

[Ethan Spessert]

+1 to this feature

[Aayush Tripathi]

+1 on this feature

[David V_ Corbin]

The issue I have with the above approach is that of traceability. Consider if there are 5 feature branches ['A'..'E'] each merged onto shared-dev-branch.  Now if is desired to merge three of them  ['A';,'C','E'] from shared-dev-branch to staging-branch.

Six months from now, there is the need to go back and review each of the features where the code originated. The "cherry-pick into a temporary branch" broke that traceability.

[Jason Newbury]

+1 to this feature

[Oscar Navarrerete Estévez]

+1 to this feature

[Alain Van Daele]

(another) +1 to this feature... 

[Tom Bonanni]

+1 to this feature

[Giles Hinton]

+1 to this feature

[Kalebe Samuel]

+1 to this feature

[George Karanastasis]

+1 to this feature

[Rich Compton]

+1 to this feature