Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,297,986
Community Members
 
Community Events
165
Community Groups

How to create a pull request with selected commits?

Edited

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?

18 answers

1 accepted

0 votes
Answer accepted

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.

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.

Like # people like this

Yes that would be great please

Like # people like this

That would be amazing!

Like # people like this

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

+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. 

Like Kalebe Samuel likes this

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

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

+1.  This is a required feature.

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

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. 

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

+1 to this feature

+1 to this feature

+1 to this feature

+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.

+1 to this feature

0 votes

+1 on this feature

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.

+1 to this feature

+1 to this feature

(another) +1 to this feature... 

+1 to this feature

+1 to this feature

+1 to this feature

+1 to this feature

+1 to this feature

+1 to this feature

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,218 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you