Feature request: the ability to create multiple pull requests for the same branch (without merging)

Issue #18084 new
Pressacco
created an issue

Ideally it would be nice if the BitBucket workflow supported...

  1. Developer writes a block of code.
  2. Developer pushes commits to BitBucket
  3. Developer creates pull request (for the code to be reviewed & approved)
  4. Developer continues writing code for the same branch.
  5. Developer pushes commits to BitBucket
  6. Developer creates pull request (for the code to be reviewed & approved)
  7. Developer continues writing code for the same branch.

The advantage here:

  1. code reviews can be performed using a Pull Request on a regular basis (A) thus allowing problems to be caught earlier in the development process (B) thus making it easier to perform the code review (i.e. looking at 100 lines of code versus 1000)
  2. the master branch is not updated until the feature is complete (A) as a result, the code base is more likely to remain stable

Is there a way to accomplish this without...

  1. constantly pushing to master, or
  2. creating yet another branch?

Comments (2)

  1. Pressacco reporter

    Possible solutions:

    1. When creating a pull request, allow the user to manually select which commits are added to the Pull Request.
    2. Offer two views in the pull request: [A] Overview - same as existing behavior (the aggregate delta of all commits), [B] Awaiting Approval (the aggregate delta of commits that have not yet been approved)

    For example:

    1. a pull request is created which includes 3 commits (A00001, A00002, A00003)
    2. code review is performed, and the following are flagged as * Approved
    3. code is not merged to master because feature development is not yet complete
    4. 2 new commits are added to the existing Pull Request (B00004, B00005)
    5. if the reviewer selected Overview they would see A00001, A00002, A00003, B00004, B00005
    6. if the reviewer selected Awaiting Approval they would see the combined delta of B00004 and B00005
  2. Pressacco reporter

    The driving force behind this request is... our office uses the following philosophies for development:

    1. commit often
    2. small regular reviews instead of one large review (to catch issues earlier in the development process, and to make the review process easier)
    3. merge to master only when the Feature or BugFix is complete (to avoid destabilizing the code base)
  3. Log in to comment