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

Expose Git level configuration options via the Stash UI

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • None
    • 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 configure certain Git repository options via the Stash UI. These options could be configured on a per-repository level.

      Options we might want to support are:

      • denyNonFastforwards
      • denyDeletes

            [BSERV-3368] Expose Git level configuration options via the Stash UI

            Stefan Saasen (Inactive) added a comment - - edited

            Note: The options that you mention are either already implemented as hooks or were suggested as hooks: https://extranet.atlassian.com/display/STASH/Hook+Examples

            The config settings you suggested are binary and affect the whole repository (i.e. all the branches and tags, even the "internal" ones). Hooks would allow us to implement more fine grained controls (i.e. certain users can force push, others can't - STASH-2586; same for branch tag deletions) in the future so I wouldn't expose the two settings you mention here. There may be other config settings (now or on the future) we could expose but we should revisit this when it becomes an issue.

            Stefan Saasen (Inactive) added a comment - - edited Note: The options that you mention are either already implemented as hooks or were suggested as hooks: https://extranet.atlassian.com/display/STASH/Hook+Examples The config settings you suggested are binary and affect the whole repository (i.e. all the branches and tags, even the "internal" ones). Hooks would allow us to implement more fine grained controls (i.e. certain users can force push, others can't - STASH-2586 ; same for branch tag deletions) in the future so I wouldn't expose the two settings you mention here. There may be other config settings (now or on the future) we could expose but we should revisit this when it becomes an issue.

            Stefan Saasen (Inactive) added a comment -

            Note: denyNonFastforwards would basically replicate the functionality that the "Reject force push" hook provides (https://confluence.atlassian.com/display/STASH/Using+repository+hooks).
            We should only have one or the other.

            Stefan Saasen (Inactive) added a comment - Note: denyNonFastforwards would basically replicate the functionality that the "Reject force push" hook provides ( https://confluence.atlassian.com/display/STASH/Using+repository+hooks ). We should only have one or the other.

              Unassigned Unassigned
              jens@atlassian.com jens
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: