We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-3141

Allow Pull Requests to source from a tag as well as a branch

    • 47
    • 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.

      Atlassian Status – May 2021

      Bitbucket Server/Data Center 7.13 (release notes) adds tags to the source selector when creating pull requests, and also enables the "Create pull request" button on the compare view when the source is a tag. When merging a pull request whose source is a tag, the "Delete ... after merging" checkbox will be disabled. Only source branches can be deleted on merge.

      The target selector still does not allow tags, and on the compare view the "Create pull request" button is still disabled when the target is a tag. This will likely never change, because merging a pull request modifies the target and Git tags are intended to be immutable.

      The source and target selectors still do not allow specific commits, and that's also unlikely to ever change. Pull requests generally include some amount of rework, which isn't possible if the pull request starts from a specific commit. Allowing it would also require substantial changes to both our API and the implementation code, both of which are heavily coupled to working with refs. Feel free to share use cases, if you have them, but the likely response will remain to either create a branch or tag on the commit you want to merge and use that.

      Best regards,
      Bryan Turner - Principal Developer
      Bitbucket Data Center

      Original suggestion

      Some branch maintenance requires the ability to pull from an annotated tag (such as in the case of a QA certified commit) to downstream branches (our branchmasters use stash for convenience). Please consider including a tab in the "source" combo box choice for tags as well as branches.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Bitbucket Data Center'
            1. Bitbucket Data Center
            2. BSERV-3141

            Allow Pull Requests to source from a tag as well as a branch

              • 47
              • 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.

                Atlassian Status – May 2021

                Bitbucket Server/Data Center 7.13 (release notes) adds tags to the source selector when creating pull requests, and also enables the "Create pull request" button on the compare view when the source is a tag. When merging a pull request whose source is a tag, the "Delete ... after merging" checkbox will be disabled. Only source branches can be deleted on merge.

                The target selector still does not allow tags, and on the compare view the "Create pull request" button is still disabled when the target is a tag. This will likely never change, because merging a pull request modifies the target and Git tags are intended to be immutable.

                The source and target selectors still do not allow specific commits, and that's also unlikely to ever change. Pull requests generally include some amount of rework, which isn't possible if the pull request starts from a specific commit. Allowing it would also require substantial changes to both our API and the implementation code, both of which are heavily coupled to working with refs. Feel free to share use cases, if you have them, but the likely response will remain to either create a branch or tag on the commit you want to merge and use that.

                Best regards,
                Bryan Turner - Principal Developer
                Bitbucket Data Center

                Original suggestion

                Some branch maintenance requires the ability to pull from an annotated tag (such as in the case of a QA certified commit) to downstream branches (our branchmasters use stash for convenience). Please consider including a tab in the "source" combo box choice for tags as well as branches.

                        bturner Bryan Turner (Inactive)
                        b5cb527bfd90 Matthew Korich
                        Votes:
                        90 Vote for this issue
                        Watchers:
                        53 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              bturner Bryan Turner (Inactive)
                              b5cb527bfd90 Matthew Korich
                              Votes:
                              90 Vote for this issue
                              Watchers:
                              53 Start watching this issue

                                Created:
                                Updated:
                                Resolved: