Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-2507

Add permission to disable branch and tag deletion via git push

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

      It would be useful to have a separate permission to disable branch and tag deletion done via git push.

      Ideally, this would be controlled independently of any permissions to delete branches and tags from the Stash web interface and is just intended to prevent accidental git push branch deletions.

          Form Name

            [BSERV-2507] Add permission to disable branch and tag deletion via git push

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3397023 ] New: JAC Suggestion Workflow 3 [ 3616171 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: BSERV Suggestions Workflow [ 2685572 ] New: JAC Suggestion Workflow [ 3397023 ]
            Daniel Zuger (Inactive) made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 417003 ]
            Daniel Zuger (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 417003 ]
            Owen made changes -
            Workflow Original: Stash Workflow [ 383434 ] New: BSERV Suggestions Workflow [ 2685572 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]

            The tag protection as part of branch protection is documented here:
            https://confluence.atlassian.com/stash/branch-permission-patterns-313461041.html
            A refernce to this documentation should suffice for now, as it provides a valid workaround, which we already use successfully.

            Christopher Timm added a comment - The tag protection as part of branch protection is documented here: https://confluence.atlassian.com/stash/branch-permission-patterns-313461041.html A refernce to this documentation should suffice for now, as it provides a valid workaround, which we already use successfully.

            Hi xabierdavila,

            I've linked to a related issue where we'll track the suggestion for better tag protection: STASH-3794.

            In the meantime, it is already possible to protect tags by using a branch pattern match and explicitly entering a pattern using the full ref form, eg: refs/tags/foo-*

            We'll get this fixed up in the documentation.

            Roger Barnes (Inactive) added a comment - Hi xabierdavila , I've linked to a related issue where we'll track the suggestion for better tag protection: STASH-3794 . In the meantime, it is already possible to protect tags by using a branch pattern match and explicitly entering a pattern using the full ref form, eg: refs/tags/foo-* We'll get this fixed up in the documentation.
            Roger Barnes (Inactive) made changes -
            Link New: This issue is related to STASH-3794 [ STASH-3794 ]
            Roger Barnes (Inactive) made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 122394 ]
            Peter Koczan (Inactive) made changes -
            Labels New: pse-request

              Unassigned Unassigned
              1dea148ed574 savviness
              Votes:
              94 Vote for this issue
              Watchers:
              83 Start watching this issue

                Created:
                Updated:
                Resolved: