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

Copy permissions when forking a repository

    XMLWordPrintable

    Details

    • 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

      Currently, when you have a repository with some permissions set up and create a new fork from it, the new repository will not have the same permissions. I'm not sure if this is the intended behavior or just not implemented, but it would be nice to be able to copy permissions from the parent repository, ideally automatically.

      The use case here is that there are main repositories to which developers have access and they create forks for their own development. It makes sense for all developers with access to the main repositories to also have access to the developer repositories. It's frustrating that when you create a pull request, the reviewer does not have access to the source repository and can't do manual testing/merge.

      If you see a use case where it's not a good idea to automatically copy the permissions, perhaps it could be an option on the permissions page.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              lalinsky Lukáš Lalinský
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Backbone Issue Sync

                  • Backbone Issue Sync is enabled for your project, but there is no synchronization info for this issue.