Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-9075

Mark my own PRs as Needs Work or Declined

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Answered
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Feedback Policy:
      We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Description

      Backstory
      My team encourages submitting PRs for review before they are ready to be merged to promote early collaboration and feedback. We were getting PRs come in on the last day of the sprint that needed A LOT of work before they could be merged. Right now, our strategy to indicate an In Progress PR is to include "WIP" or "DO NOT MERGE" in the PR Title / Description fields.

      Problem
      This naming strategy works most of the time, but sometimes we have In Progress PRs that are getting merged into our main branch early.

      Suggestion
      When I submit a PR for review before I am ready for that PR to be merged, I would like to mark that PR as "Needs Work" until I am ready to merge it. Once I am ready to merge it, I would like to remove this status so that others know to go through it one last time and approve it if the code adheres to our guidelines. I wouldn't want to mark my own PR as "Accepted", because that would probably mess with our current requirement of having two reviewers accept the PR before it can be merged. However, if something went horribly wrong, I might want to mark my own PR as "Declined".

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              shannonbeagin1561878682 Shannon Beagin
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: